Create Blender scene bridge

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

Annotations already indicate the tool is write-capable (readOnlyHint=false) and open-world (openWorldHint=true). The description adds the concept of a 'scaffold' and metadata workflow types, but does not disclose specifics like what operators are created or whether the network is modified. With annotations providing the safety profile, this adds some but not rich behavioral context.

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, dense sentence that front-loads the primary action ('Create') and clearly specifies the deliverable and purpose. No filler or redundant content.

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 10-parameter creation tool with no output schema and low parameter coverage, the description is under-specified. It does not explain what the scaffold includes, prerequisites, or how the selected parameters affect the result, leaving significant gaps for the agent to infer.

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 20%, leaving 8 of 10 parameters undocumented in the schema. The description does not compensate by explaining parameters; it only lists workflow types that loosely map to the 'handoff_mode' enum. Most parameter meanings remain opaque, so the description adds minimal value over the sparse schema.

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 clearly states the tool's function: 'Create a Blender-to-TouchDesigner scene handoff scaffold' with specific workflow types (file-watch, OSC, WebSocket). This distinguishes it from sibling tools like blender_scene_import (which imports models) by emphasizing the handoff scaffold aspect.

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 description provides context by naming the three supported workflow types, implying when the tool would be used. However, it does not explicitly state when to use this tool over alternatives or provide exclusions, leaving usage guidance implied rather than explicit.

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