connect_to_musescore

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

No annotations are provided, so the description must cover behavioral traits. It mentions the plugin requirement and that it connects via WebSocket, but it does not detail error handling, what happens on duplicate connections, or side effects beyond establishing a connection.

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: two sentences for the purpose and prerequisite, followed by parameter descriptions. It is front-loaded with the core action.

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 two simple optional parameters and an output schema (not shown but present), the description provides enough context to use the tool correctly. It lacks details on return values or error conditions, but the output schema likely covers that.

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 schema has 0% description coverage, but the description adds meaning by explaining 'host: WebSocket host (default: localhost)' and 'port: WebSocket port (default: 8765).' This clarifies the purpose of each parameter beyond the schema's defaults and titles.

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 verb 'Connect to' and the resource 'a running MuseScore instance'. It distinguishes from sibling tools like 'connect_to_dorico' and 'connect_to_sibelius' by specifying MuseScore.

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?

It explicitly states the prerequisite: 'The MuseScore MCP Score Bridge plugin must be running.' This informs when to use the tool. However, it does not explicitly mention when not to use it (e.g., if already connected) or suggest alternatives.

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