Set up output

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

Annotations indicate non-read-only (modifies state) and non-destructive with open-world hint. Description adds that routing can create streams or recordings, but does not elaborate on side effects like requiring permissions or affecting external systems. Some context beyond annotations, but not rich.

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?

Single sentence that is front-loaded with verb and resource, listing key output types. No unnecessary words; every word earns its place.

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 5 parameters and no output schema, the description is too brief. It does not explain the required source_path parameter, conditional usage of record_format, or what happens after routing. Lacks completeness for a tool of this complexity.

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 low (20% – only source_path described). Description adds meaning by enumerating output types matching the output_type enum, but does not explain resolution, record_format, or parent_path parameters. Partially compensates for low coverage but insufficient.

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?

Description uses specific verb 'Route' and resource 'TOP to an output', listing distinct output types (display window, NDI, Syphon/Spout, recording, Touch Out). This clearly differentiates from sibling tools like create_multi_output or render_output.

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?

Description implies usage is for routing a TOP to an output, but does not provide explicit guidance on when to use this tool versus alternatives like create_multi_output or render_output. No when-not or exclusion criteria are given.

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