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

The description reveals that pose generation has no job ID, making this the correct polling mechanism, and explains the meaning of the status fields (pending, done, error) and the stall condition. This goes beyond the annotations, which only declare read-only and idempotent hints.

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 well-structured, with each sentence providing necessary context: field list, usage scenario, and stall warning. It is concise yet complete without any redundant or irrelevant 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?

Given the tool's role in the generation workflow, the description covers all necessary aspects: field enumeration, status semantics, integration with generate_pose and generate_character_animation, and troubleshooting guidance for stalled poses. It is fully self-contained for a user to understand when and how to use it.

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 only parameter, characterId, is described in the schema as 'Character id.' The description adds no further meaning or context for this parameter, so it does not enhance understanding beyond the schema. Since schema coverage is 100%, a baseline of 3 is appropriate.

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 the tool lists all poses on a character, enumerates the returned fields, and explains its role as the poll target after generate_pose and source for generate_character_animation, distinguishing it from related tools.

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 explicitly states when to use this tool: after generate_pose to poll for completion, and to fetch ready pose IDs for generate_character_animation. It also warns about interpreting 'pending long after pendingSince' as a stall, providing actionable guidance.

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