get_animation_info

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

With no annotations, the description carries the full burden of behavioral disclosure. It provides no information about whether the operation is read-only, what happens if the animation or library path is invalid, or what the response format is. This is a significant transparency gap.

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 extremely short, but it merely restates the tool name in sentence form without adding substantive value. It is under-specified rather than concisely informative, so it does not earn its place as a useful addition.

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?

This is a simple tool with no output schema and no parameter details in the description. The description gives no indication of what 'info' means, what the return value contains, or how the parameters relate to each other. Given the sibling tools, this lacks the contextual depth needed to use the tool correctly.

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?

Schema description coverage is 0%, and the description fails to explain the purpose or format of the two required parameters: 'library_path' and 'anim_name'. Without any parameter-level context, the user must infer from the parameter names alone, which is insufficient for a tool that may require exact path specifications.

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 'Get info about an animation' clearly states a get operation targeting animation info. It distinguishes itself from sibling tools like 'get_resource_info' by explicitly mentioning animations, and it is specific enough to indicate a read action on a single animation resource.

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 provides no guidance on when to use this tool versus alternatives. It does not mention related tools like 'get_resource_info' or explain scenarios where animation-specific info is needed, nor does it note any prerequisites.

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