Fix Tool interface javadocs and generic types

[dbwiddis]

Description

Adds generic types to Tool interfaces

Issues Resolved

In support of #1161 , #1521, #1545, #1546, #1547, #1548

Check List

• New functionality includes testing.
  • All tests pass
• New functionality has been documented.
  • New functionality has javadoc added
• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[dbwiddis]

Windows (17) test failure not associated with this PR:

46 tests completed, 1 failed, 9 skipped
Tests with failures:
 - org.opensearch.ml.rest.RestMemoryGetConversationsActionIT.testGetConversations_nextPage

Linux (11) test failure not associated with this PR:

765 tests completed, 1 failed, 55 skipped
Tests with failures:
 - org.opensearch.ml.action.prediction.PredictionITTests.testPredictionWithDataFrame_LinearRegression

[ylwu-amzn]

Hi, @dbwiddis we are developing agent framework in feature branch now, please cut PR to feature branch : feature/agent_framework_dev,

BTW, are you or @jngz-es working on tool framework now?

[dbwiddis]

Hi, @dbwiddis we are developing agent framework in feature branch now, please cut PR to feature branch : feature/agent_framework_dev,

OK, I've updated the target branch, but then this just becomes a fixup of a few files. I expect that adding the generic types probably broke several committed POC files that implement the interfaces, though, so I'll have to update them now.

How will these interfaces and the Agent Framework that uses them be made available for import by other projects?

BTW, are you or @jngz-es working on tool framework now?

At the moment I am trying to complete #1547 which is the CatIndices tool. But you have already written it on this branch. So what is the tasking for #1547?

[ylwu-amzn]

Thanks @dbwiddis .

How will these interfaces and the Agent Framework that uses them be made available for import by other projects?

For development phase, we can use maven local. We will publish to maven central when release just like ml client.

But you have already written it on this branch. So what is the tasking for #1547?

For now the PoC is workable , we don't consider edge cases, permissions, testing etc. To make it prod ready, we need to fill the gap to make it robust, performant and secure.

[dbwiddis]

For now the PoC is workable , we don't consider edge cases, permissions, testing etc. To make it prod ready, we need to fill the gap to make it robust, performant and secure.

How are we tracking which classes on this branch have been "productionized"?

[jngz-es]

LGTM