render_score

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

No annotations exist, so the description carries the full burden. It does add real value by disclosing the return shape and the remote-vs-local difference between downloadPath and path, plus the default soundFont. However, it never says whether rendering is synchronous or long-running, how expensive it is, or how failures surface — material gaps for an audio-rendering tool.

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?

A single dense paragraph with no filler sentences; every clause conveys semantics or output information. It is somewhat run-on, and the return-value note is buried mid-sentence rather than front-loaded as a separate line.

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 deeply nested input schema with no output schema and no annotations, the description covers the score model thoroughly and explains the return payload. What is missing is operational context — sync versus async behavior, and how this tool relates to the generation siblings — which leaves a small but real gap.

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 description goes well beyond the schema: it explains units and conventions (bar/beat 1-based, pitch as MIDI note number, length in beats), what program means (GM instrument number) versus drums, and what role does (selects default level) with its enumerated values. It also lists the installed soundFont IDs and the default, none of which appear in the schema.

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?

Opens with a specific verb+resource+output: rendering an arranged score into a mixed-down WAV, and names exactly what comes back (id, duration, audio location). This is clearly distinguishable from siblings like generate/submit_generation/get_generation, which operate on a different pipeline.

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?

Usage is only implied by the object shape: the caller must supply a score with tempo, timeSignature and tracks. There is no explicit statement of when to pick render_score over generate or submit_generation, and no prerequisites or exclusions are given.

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