Connect Isadora patch

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the agent knows this is a mutating but non-destructive operation. The description adds context about what is created (actor, watcher, scene exchange scaffold) and 'stable namespace mapping', but doesn't disclose further behavior like prerequisites or side effects.

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 that is front-loaded with the verb and key resource. There is zero waste and every word adds meaning, making it appropriately concise.

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 only basic annotations, the description needs to explain more about the scaffold's behavior, return values, or prerequisites. It only provides a high-level purpose, leaving significant gaps for a complex 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?

Schema description coverage is only 20% (2 of 10 parameters have descriptions). The description doesn't explicitly define any parameter meanings; it merely hints at concepts via 'actor', 'watcher', 'scene', and 'namespace'. This doesn't sufficiently 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 uses a specific verb ('Create') and resource ('Isadora OSC actor, watcher, and scene exchange scaffold') with an additional qualifier ('stable namespace mapping'). This clearly distinguishes it from other connection tools like connect_max_msp_bridge or connect_ableton_link_session, though it doesn't explicitly mention 'connect' as an action.

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 implies usage for Isadora OSC integration but doesn't provide explicit when-to-use or alternative guidance. It lacks exclusions or comparisons to sibling connect tools, so guidance is only inferred from the purpose.

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