Connect Isadora patch

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

Annotations indicate a non-readonly, open-world, non-destructive operation. The description adds that it creates a scaffold with stable namespace mapping, but does not disclose side effects like node creation, network modifications, or whether existing components are affected. It is consistent with annotations but not enriching.

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, well-structured sentence with no redundant wording. It front-loads the action (Create) and key components, making it easy to parse quickly.

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 with 10 parameters and complex integration scope, the description is too minimal. It does not explain what the scaffold entails, how actor/watcher/scene elements interact, or what the output of the operation is. The agent would lack essential context for correct invocation.

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), and the description does not explain critical parameters like send_port, receive_port, actor_count, watcher_count, scene_count, isadora_host, or active. The description adds no meaningful parameter semantics and fails to 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 identifies the tool as creating an Isadora OSC scaffold with actor, watcher, and scene exchange components, and references stable namespace mapping. This distinguishes it from other connect_* tools by specifying Isadora and OSC, though 'scaffold' is somewhat abstract and doesn't fully detail the operations.

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 guidance is given on when to use this tool versus alternatives such as other connect_* or create_* tools. The description lacks any mention of prerequisites, exclusions, or typical scenarios, leaving the agent without explicit usage context.

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