connect_to_dorico

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

No annotations are provided. The description reveals that the tool establishes a WebSocket connection and returns connection status and Dorico information. However, it does not disclose error handling, idempotency, or reconnection behavior. While adequate, more detail would improve transparency.

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 extremely concise with two sentences, each adding necessary information. It front-loads the purpose and immediately states the key usage rule. No unnecessary words 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 the tool has no parameters and an output schema is present, the description covers the essential aspects: what it does, when to use it, and what it returns. It could mention potential failure modes or timeouts, but for a simple connection tool, it is largely complete.

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?

The input schema has no parameters, and schema description coverage is 100% (trivially). With 0 parameters, the baseline is 4. The description does not need to add parameter info, as there are none to document.

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 'Connect to Dorico' and 'Establishes a WebSocket connection to Dorico's Remote Control API,' specifying the exact verb and resource. It is distinct from sibling tools which focus on musical tasks, making its purpose unambiguous.

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 explicitly states 'Must be called before using other Dorico tools,' providing clear context on when to use this tool. It does not mention when not to use it, but for a connection tool the required precedence is well conveyed.

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