render_score

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does well: it states that an existing output file is overwritten, that PNG export writes one file per page with a -1, -2 suffix, and that the output extension must match the format. It also explains the executable discovery process. It does not mention potential failure modes (e.g., missing MuseScore, invalid input), but the installation requirement is disclosed.

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 well-structured with a clear first sentence, then a paragraph on requirements, a paragraph on executable discovery, and an Args section. It is slightly long but every sentence earns its place, covering installation, discovery, and parameter semantics. The front-loaded first sentence gives the core purpose immediately.

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's complexity (external dependency, multiple formats, output path behavior), the description is quite complete. It covers installation, executable discovery, input types, format-specific behavior (PNG pagination), and output overwriting. It does not describe the output schema/return value, but an output schema exists, so that is not required. Minor gaps: no explicit error-handling or exit-code behavior, but the essential context is present.

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 0%, so the description must compensate. It does: it explains input_path as the path to the score file, format as one of the six values with a default, and output_path as the destination with default behavior and extension-matching requirement. This adds meaning beyond the bare schema properties, though it could be slightly more explicit about the exact format enum values (it does list them).

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 states a specific verb ('Render') and resource ('a score file') and enumerates the exact output formats (PDF, PNG, MIDI, MP3, WAV, MusicXML). It clearly distinguishes this from the live-connection siblings (connect_to_musescore, add_live_note, etc.) by emphasizing it runs the MuseScore Studio 4 command line and does not need a live connection.

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 when to use this tool: to render a score file to various formats, and it clarifies that MuseScore Studio 4 must be installed but need not be running. It also explains the input file types (MusicXML, .mscz, .mid) and how MuseScore is located, including the MCP_SCORE_MUSESCORE_PATH environment variable fallback. This gives clear context for when this tool is appropriate versus the live-connection siblings.

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