compare_animations

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

With no annotations provided, the description must disclose behavioral traits. 'Compare' implies a read-only operation, but it doesn't state this explicitly, nor does it reveal what happens during comparison (e.g., whether it just returns differences or also performs validation). The output schema exists, but the description doesn't clarify the nature of the comparison result.

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 concise and front-loaded, with the tool's purpose stated first and parameters cleanly listed in an Args block. It avoids unnecessary wording and is well-organized for a tool with only two parameters.

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?

For a tool with no annotations and no information about what 'compare' entails, the description is incomplete. While the output schema exists, the description doesn't explain what kind of comparison is performed or what criteria are used, which is essential for an agent to select and invoke this tool correctly among the many sibling tools.

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%, so the description must compensate. It does add meaning by labeling path_a and path_b as 'First animation asset path' and 'Second animation asset path', which is slightly more informative than the schema's 'Path A' and 'Path B'. However, it lacks details on path format or expected asset types.

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 uses the specific verb 'Compare' with the resource 'two animation assets', which clearly distinguishes it from the many getter and mutation tools in the sibling list. However, it doesn't specify what aspect of the animations is compared (curves, notifies, bones, etc.), leaving some ambiguity.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention what kind of comparison it performs, nor does it contrast with sibling tools like get_animation_summary or search_animations. The description simply states what it does without context.

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