Adding new Tool Call "Annotations" to tool macro

[abhay-agarwal]

I added the new tool annotation feature to the tool call macro. Currently it just parses the annotation field as json, so that one might potentially be able to simply copy and paste the field from elsewhere into the macro invocation. This might not be optimal for several reasons, one being that the signature must be written in camel case, with no indication to the user that a non-camel-cased value is incorrect, even if they looked at the expanded macro. A solution to this would be to create a wrapper over ToolAnnotations (or annotate ToolAnnotations itself) with deny_unknown_fields. However, this would also prevent the annotation macro from being future proof (currently if the annotation were to be deprecated, then we could silently ignore it).

Here's an example usage taken from the test I added

        #[tool(
            name = "direct-annotated-tool",
            annotations = {
                title: "Annotated Tool", 
                readOnlyHint: true
            }
        )]
        pub async fn direct_annotated_tool(&self, #[tool(param)] input: String) -> String {
            format!("Direct: {}", input)
        }

[4t145]

LGTM

I need to fix ci error introduced by lasted merge before merge this.

[4t145]

Could you please merge the main branch and then we can run ci again? Also fix the commit message ci by the way.

[abhay-agarwal]

Could you please merge the main branch and then we can run ci again? Also fix the commit message ci by the way.

Sounds good, I just squashed and reworded.

[4t145]

Ci failed again but never mind, I will make it lowercase when merge. And thank you for PR.