connect_to_sibelius

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

No annotations, so description carries burden. Mentions WebSocket connection, version requirement, and no plugin needed. Does not describe expected return value, potential errors, or that it is a prerequisite for other Sibelius tools.

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?

Very concise with a brief intro and args section. No wasted words. Purpose is front-loaded.

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 simple connection tool with 2 optional parameters, description covers essential aspects. Lacks details on return value or validation, but output schema may provide 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?

Schema coverage 0% but description explains both parameters: host (default localhost) and port (default 1898, Sibelius Connect default). Adds meaning beyond schema with defaults and typical use.

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?

Clearly states it connects to a running Sibelius instance via Sibelius Connect. Specifies version requirement (2024.3+) and that no plugin is needed. Distinguishes from siblings that connect to different apps (Dorico, 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?

Provides context: requires Sibelius Ultimate tier and a WebSocket server. Gives default ports. Does not explicitly state when not to use or alternatives, but sibling tools for other apps make it implicit.

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