Connect Syphon/Spout router

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

Annotations already indicate this is not read-only and not destructive, so the bar is lower. The description adds that it is a 'scaffold' and 'platform-gated,' providing some context. However, it does not disclose any side effects, permissions needed, or behavioral nuances beyond creation, so it only partially covers the burden with annotations present.

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 sentence, front-loaded with the verb 'Create,' and uses concise language. It is appropriately sized but includes jargon like 'platform-gated' that might need elaboration. Still, it earns a high score for efficiency.

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 7 parameters, no output schema, and a complex domain (Syphon/Spout), the description is too minimal. It does not explain what the scaffold entails, how route maps are structured, platform requirements, or what 'explicit setup notes' contain. An agent would lack sufficient context to invoke this tool confidently.

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 coverage is 57% (4 of 7 parameters have descriptions), which is moderate. The description does not explain any parameters directly, only mentioning 'route maps' which could be related to route_count but is not explicit. Since coverage is below 80%, the description should compensate but does not.

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 uses the verb 'Create' with a specific resource: 'a platform-gated Syphon/Spout texture-sharing router scaffold with route maps and explicit setup notes.' This is distinct from generic actions and mentions platform gating. However, it does not differentiate from similar sibling tools like connect_ndi_router_matrix or osc_router_matrix.

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?

There is no guidance on when to use this tool versus alternatives, no mention of prerequisites, and no scenarios provided. The description simply states what it does without any context for selection.

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