production.animation_generation_compatibility

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

Annotations already declare this is a non-read-only, non-idempotent mutation, so the bar for extra behavioral context is lower. The description adds meaningful traits beyond annotations: default plan mode (apply=false), generation as an immutable plan.json reference, source Actions retained, and unsupported adapters returning concrete errors. These details materially inform safe invocation.

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 single dense sentence is poorly front-loaded: it opens with a meaningless 'high-level M6 unit' rather than the tool's purpose. Semicolon-joined clauses mix purpose, workflow, parameter meaning, and error behavior without clear structure, forcing the agent to parse jargon before reaching actionable information.

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 7-parameter mutation tool with 0% schema description coverage, the description should be far more complete. Output schema and annotations cover return values and safety, but the description lacks a clear purpose statement, tool-selection guidance, and documentation for four of seven parameters.

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 coverage is 0% across 7 parameters, so the description must carry parameter meaning. It explains three parameters partially: apply defaults to false (plan mode), generation is the immutable plan.json reference, and options carries stage parameters, thresholds, or visual review. It says nothing about brief, intent, object_name, or operation_id, leaving nearly half the inputs unexplained.

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 never states a clear verb-and-resource purpose like 'check animation generation compatibility against a rig.' Instead it opens with 'high-level M6 unit,' which is jargon an agent cannot act on, and only implies a compatibility/planning operation through phrases like 'explicit mapping and compatible body rig required.' It does not distinguish this from animation_generation_plan or rig_compatibility_report in plain terms.

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?

It gives one procedural hint ('Plan first, apply=false by default'), but does not say when to use this tool versus the many sibling compatibility and generation tools. Phrases like 'technical QA and temporal artistic review are distinct' suggest a workflow but name no alternatives or selection criteria, leaving the agent to guess.

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