Create Blender scene bridge

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

Given the annotations already indicate this is a write operation (readOnlyHint false) with potential external effects (openWorldHint true), the description adds little behavioral context. It does not describe what the scaffold consists of (e.g., a baseCOMP, CHOP/DAT nodes, or external files), nor does it mention side effects or prerequisites. The description only restates the general purpose without elaborating on the actual behavior beyond the annotations.

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, well-structured sentence that front-loads the verb and resource. It includes the key scope (Blender-to-TouchDesigner handoff) and the three workflow modes with zero wasted words. No redundancy or filler.

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?

With 10 parameters, no output schema, and no nested objects, the description is far too minimal. It does not explain what a 'handoff scaffold' comprises, what the agent can expect after execution, or how the modes and parameters interact. The description provides only the high-level concept, leaving an agent without enough information to correctly configure or validate the tool's behavior.

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% (2 of 10 parameters documented), so the description should compensate. It mentions 'file-watch, OSC, or WebSocket' which loosely maps to the handoff_mode enum, but it does not explain any of the other parameters (asset_format, sync_camera, receive_port, etc.) or how the workflows relate to the bridge's operation. This leaves the agent with little guidance for parameter selection.

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 specific verb 'Create' and names a clear resource: a 'Blender-to-TouchDesigner scene handoff scaffold'. It also specifies the supported workflows (file-watch, OSC, or WebSocket metadata), which clearly distinguishes it from sibling bridge tools like create_unreal_livelink_bridge or create_shared_memory_bridge.

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 implies its use case by naming the integration (Blender-to-TouchDesigner) and the three handoff modes, but it does not explicitly state when to use this tool versus alternatives, nor does it provide exclusions or prerequisites. The context is present but not fully developed.

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