execute_blender_handoff

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

Annotations already declare non-readonly, non-destructive, closed-world behavior, so the bar is lower. The description still adds real value: it discloses an idempotency contract via receipt reuse, uncertainty handling after dispatch, and what a character handoff produces (an animated GLB).

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?

Three compact sentences, front-loaded with the core action, with no filler. The final line about animated GLB is slightly tangential to invocation but is short enough not to hurt.

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-value explanation is unnecessary, and annotations cover the safety profile. However, for a four-parameter mutation tool with 0% schema description coverage, the complete absence of parameter guidance leaves a meaningful hole an agent could stumble on (e.g., what attempt and sample_index control).

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 none of the four parameters (job_id, attempt, source_kind, sample_index) are explained in the description. The mention of 'character handoffs' vaguely gestures at the source_kind enum but does not clarify its meaning, and attempt/sample_index are entirely unaddressed.

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?

States a specific verb and resource: 'Run only the prepared fixed script in the connected local Blender and verify its exports.' The word 'prepared' implicitly distinguishes it from the sibling 'prepare_blender_handoff' and from 'execute_unreal_handoff', though it never names them explicitly.

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?

Provides useful operational guidance for retry semantics ('A completed receipt is reused. After an uncertain dispatch inspect the receipt before a new attempt'), but that guidance is implied rather than routed to a named tool (likely get_handoff_report). There is no explicit when-to-use-vs-alternatives statement relative to prepare_blender_handoff.

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