get_animation_info

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden of behavioral disclosure. It accurately lists the returned data fields, but does not explicitly state that the operation is read-only, what happens if the animation doesn't exist, or the exact structure of the response. This is a getter, so the read-only nature is somewhat implied.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, information-dense sentence that front-loads the key function. It avoids filler and is appropriately sized for the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description lists the data returned but omits the exact structure of the return value and fails to explain parameter semantics. Given the lack of an output schema and annotations, more detail would be needed for reliable invocation and response parsing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has zero description coverage and the description does not elaborate on the parameters. While 'animation' is self-explanatory, 'node_path' is ambiguous—it could refer to the path of the AnimationPlayer or the animation resource. The description does not clarify the expected format or how the parameters interact.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific verb and resource: retrieving a single animation's length, loop mode, step, and all track keyframe data. This distinguishes it from sibling tools like list_animations or get_animation_tree_structure, which have different scopes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use when detailed info about a specific animation is needed, but it does not explicitly contrast it with alternatives like list_animations or get_animation_tree_structure. There is no 'when not to use' guidance, so the agent must infer usage from the context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.