analyze_retarget_profile

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

With no annotations, the description must disclose behavior, but it only says 'Measure', which implies a read-only operation without confirming side effects or lack of mutations. It fails to mention return format, potential errors, or any safety guarantees.

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 sentence, which is brief but severely under-specified. It omits critical information like parameter roles, expected inputs, and output semantics, making it more under-specified than concise.

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 high complexity of the input schemas (nested object types, many fields) and the existence of an output schema, the description lacks completeness. It doesn't explain what 'measure safety' means in terms of return values or how the tool evaluates the bone map against the provided rigs and scene.

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 schema contains 4 complex parameters (profile, source_rig_id, target_rig_id, scene_snapshot) with 0% description coverage. The description provides no explanation of what these parameters mean or how they are used, leaving the agent without essential semantic guidance.

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 verb 'Measure' and specifies three measurable aspects (hierarchy, rest-axis, proportion safety) for a reviewed bone map. This distinguishes it from sibling tools like validate_retarget_profile, though the phrase 'reviewed bone map' is somewhat unclear and doesn't explicitly reference the profile object.

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 such as validate_retarget_profile or suggest_retarget_profile_map. The description gives no context for selection or preconditions.

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