Connect Syphon/Spout router

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

The description adds minor behavioral context: the tool creates a scaffold including 'route maps' and 'setup notes'. It does not contradict the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false), but it also doesn't disclose concrete side effects, such as whether existing operators are modified, what files/systems are touched, or if re-running is safe.

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, which is concise, but it packs in undefined jargon ('platform-gated', 'route maps') and front-loads no newbie-friendly orientation. It earns a middle score because brevity is present but at the expense of comprehensibility.

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 tool that creates a scaffold in a TouchDesigner project (inferable from parent_path param), with 7 parameters and no output schema, the description should clarify what gets created, return values, prerequisites, and side effects. It does none of this, leaving an agent underinformed for a moderately complex generative operation.

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?

The schema covers 57% of parameters with descriptions, but the tool description mentions no parameters at all. Terms like 'platform-gated' hint at mode/source selection but don't explain how the parameters map to behavior. The description does not compensate for the schema's gaps (e.g., 'mode' and 'active' lack descriptions).

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 a clear verb ('Create') and names a specific resource ('Syphon/Spout texture-sharing router scaffold') with additional features ('route maps', 'setup notes'). It is clearly distinct from sibling tools focused on other routing technologies (e.g., NDI, SDI). However, 'platform-gated' is jargon that obscures the exact mechanism, preventing a perfect score.

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 explicit guidance on when to use this tool or when to prefer an alternative. The name and domain imply usage for Syphon/Spout texture sharing, but the description itself provides no context, prerequisites, or exclusions—leaving the agent to guess.

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