Connect Unity OSC bridge

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

Annotations already indicate a non-read-only, non-destructive, open-world operation. The description adds no additional behavioral details about side effects, what gets created, prerequisites, or network setup. It merely says 'Create... scaffold' without explaining consequences or environment changes.

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 with no filler. It conveys core concepts efficiently, though the phrase 'notes' is vague. Overall it is appropriately concise for a scaffold-creation tool.

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 further elaboration, this one-sentence description is insufficient. It does not explain what the scaffold includes, what the user should expect after invocation, or how the preview handoff and OSC network behave.

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%, so the description should compensate. It mentions object transforms, events, and NDI/Syphon notes, which loosely map to object_count, event_count, and preview_mode, but it does not explain any parameter semantics such as ports, hosts, namespace, or parent_path.

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 states a specific verb ('Create') and resource ('Unity OSC and preview handoff scaffold'), and clarifies scope by mentioning object transforms, events, and NDI/Syphon notes. This distinguishes it from other bridge tools in the sibling list, which target different external systems.

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?

No guidance is given about when to choose this tool over alternatives, such as other connect_* bridges or the generic connect_oscquery_namespace. The context ('Unity OSC') is implicit from the name, but there is no explicit when-to-use or when-not-to-use direction.

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