production.character_compare_reference

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

The annotations already disclose that this is a non-read-only, non-idempotent, non-destructive operation. The description adds useful context that it produces paired images for review and does not claim semantic equivalence, but it does not explain write targets, permissions, repeated-call behavior, or artifact retention.

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 a single front-loaded sentence with no filler, and the semicolon cleanly separates purpose from limitation. The phrasing is dense and slightly cryptic, so it is concise but not maximally clear.

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 non-idempotent comparison tool with 0% schema coverage and many sibling compare/analysis tools, the description should explain prerequisites, parameter meaning, and preferred usage relative to alternatives. It supplies only a high-level purpose and a limitation, leaving significant gaps.

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 carries the full burden for explaining object_name, reference_set, and operation_id. It only partially clarifies reference_set by mentioning a 'reference view set' and says nothing about object_name or operation_id.

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 states a specific comparison basis (silhouette differences against a reference view set) and the produced artifact (paired images for review), which is more than a restatement of the name. It does not name the closest sibling alternatives such as character_compare_before_after or retopology_compare_silhouette, so sibling differentiation is left implicit.

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 phrase 'against a reference view set' implies a prerequisite and context for use, and 'no semantic-equivalence claim' sets a boundary on interpretation. However, there is no explicit guidance on when to choose this tool over sibling comparison tools, nor any named alternative.

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