ATEM switcher control

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

The description adds behavioral context beyond annotations by clarifying that it does not use the Blackmagic SDK directly, builds an offline-safe matrix, and includes specific functions (cut/auto/FTB, program/preview selection). This is useful since annotations only indicate non-read-only, non-destructive, and open-world hints. No contradiction.

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 two concise sentences. The first sentence states the primary action and routing options, the second clarifies the technical approach and scope. No filler or redundancy.

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 six parameters fully described in the schema and no output schema, the description explains the tool's purpose, method (OSC relay), and key capabilities. It is complete enough for an agent to understand what the tool does and when to use it, though it could briefly mention the 'inputs' parameter's effect on the created matrix.

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 100%, so the baseline is 3. The description does not add specific parameter semantics beyond what the schema already provides for host, port, inputs, etc. It mentions 'cut/auto/FTB and program/preview' which implies input selection but does not elaborate on parameter syntax or constraints beyond the schema.

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's function: 'Create an OSC control preset for an ATEM switcher routed through atemOSC, Bitfocus Companion, or another OSC relay.' It specifies the verb (create), the resource (OSC control preset), and distinguishes itself from direct SDK tools and sibling tools like 'connect_blackmagic_atem' by emphasizing it builds an offline-safe TouchDesigner OSC 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?

The description provides clear context for when to use this tool: when routing through atemOSC, Companion, or another OSC relay, and when you need an offline-safe preset without SDK access. It does not explicitly name alternatives or exclusions, but the context is sufficiently clear to guide selection.

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