Connect Unity OSC bridge

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

With annotations indicating openWorldHint=true and destructiveHint=false, the description adds some context by specifying it creates a scaffold for transforms, events, and NDI/Syphon notes. However, it does not disclose what a 'preview handoff' entails, whether it creates a COMP in the network, or any side effects beyond the creation.

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, front-loaded sentence that clearly communicates the core action and purpose. It contains no redundant or filler words, making it concise and easy to parse.

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 tool has 10 parameters and no output schema, the description is too terse to be complete. It does not explain the overall workflow, what the scaffold consists of, how preview handoff works, or any prerequisites. An agent would need significant additional information to invoke this tool correctly for real-world scenarios.

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%, and the description barely compensates. It only hints at parameters like object_count, event_count, and preview_mode through 'object transforms, events, and NDI/Syphon notes', but does not explain send_port, receive_port, namespace, active, etc. The description adds minimal value beyond the schema, leaving most parameters under-documented.

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 creates a Unity OSC bridge scaffold, specifically mentioning object transforms, events, and NDI/Syphon preview handoff. This distinguishes it from sibling bridge tools like those for Unreal or other external systems, making the purpose unambiguous.

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 tool's usage is implied by its name and description: it is for connecting to Unity via OSC with preview support. However, it does not explicitly state when to use this versus alternative bridge tools (e.g., Unreal LiveLink) nor any prerequisites like running Unity, which would be helpful given the large set of sibling bridge creators.

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