Connect MadMapper surface

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the agent knows this is a creation operation. The description adds that it creates a scaffold with handoff notes, but does not disclose side effects, prerequisites, or what the scaffold entails. Given the annotations cover the mutation aspect, this is adequate but minimal.

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, focused 18-word sentence that is front-loaded and contains no filler. It conveys the essential purpose without 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?

With 10 parameters, no output schema, and minimal annotations, the description is too terse to be complete. It doesn't explain what the scaffold will include, how to configure the handoff, or what the function returns. For a creation tool of this complexity, more context is needed.

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 40% (4 of 10 params described). The description mentions OSC and Syphon/Spout/NDI handoff, which maps to handoff_mode and ports, but does not explain media_count, surface_count, active, or other parameters. It does not compensate for the low schema coverage.

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 specific action (Create) and resource (MadMapper OSC surface/media control scaffold), and adds detail about source handoff options (Syphon/Spout or NDI). This distinguishes it from sibling tools that connect to other software or create generic control surfaces.

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 offers no guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or reference any sibling tools, which is a gap given the large number of similar connect/create tools in the sibling list.

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