validation.prop_handoff

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

Annotations already declare readOnlyHint and idempotentHint; the description's 'Risk: read' simply echoes that. It adds only a maturity level and a vague policy reminder, neither of which explains observable behavior such as what the validation checks or what side effects are possible.

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 text is short, but brevity here is under-specification: the first clause merely restates the tool name, and the remaining clauses are boilerplate metadata rather than informative content. A concise definition would still state the operation and key inputs.

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 command with 11 parameters, 7 required, and a non-obvious domain concept (prop handoff), this description leaves the agent with no basis for choosing the tool or constructing a valid call. The output schema does not compensate for the missing purpose and parameter semantics.

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 only 27% and the core parameters (armature, bone, catchFrame, constraintName, frameStart, frameEnd, object) have no descriptions. The tool description does not compensate by explaining any of these parameters or how they relate to a prop-handoff validation.

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 only names the command (`validation.prop_handoff`) and labels it with risk/maturity metadata; it never states what the tool does, what resource it acts on, or what a prop handoff validation entails. It is essentially a restatement of the tool name and therefore fails to distinguish this from sibling validation 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?

There is no guidance about when to call this tool versus alternatives such as blender_validation_floor_penetration or blender_validation_limb_length. The note that per-request argument checks and session policy apply is generic harness policy, not usage direction.

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