production.animation_deformation_qa

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

Annotations declare readOnlyHint=false, idempotent=true and destructive=false, so the agent knows this is a non-destructive but writing operation, yet the description never says what is written (a QA report? a cache?) or where results land. It also leaves the 'supplied contact events' precondition unexplained — whether contact data must be produced beforehand is a crucial behavioral fact.

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?

A single short sentence with no padding, but it is front-loaded with an internal prioritization rule ('Prioritize pose extremes, high angular changes...') rather than the tool's purpose, so the most useful information arrives last.

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?

An output schema exists, so return values needn't be described, but the description is still far too thin for a tool whose three parameters are undocumented and whose write side-effects are unstated. It also gives no notion of what 'weighted mesh deformation' evaluation criteria produce, which an agent needs to decide whether to call it at all.

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 supplies no parameter meaning at all: object_name, action_name and the opaque free-form options object are entirely undocumented. The phrase 'supplied contact events' is the only oblique hint that options may carry contact data, which is insufficient for a 3-parameter tool with a schemaless nested object.

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 names an evaluation of 'weighted mesh deformation', which hints at a QA/analysis of how a mesh deforms over an animation. But the leading clause about prioritizing pose extremes and contact events reads as implementation detail and never states plainly that this is an animation-deformation QA pass. It also fails to distinguish it from siblings like production.character_deformation_qa, production.deformation_analyze or production.facial_deformation_qa.

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?

There is no guidance on when to run this versus deformation_analyze, character_deformation_qa, or animation_analyze_motion_quality. No prerequisites (must an action exist first? must contacts be supplied?) and no exclusions are stated.

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