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

Annotations cover the flag profile (readOnly=false, idempotent=false, openWorld=true), and the description adds cost (10 Gold), latency (~5-30 s), and a nuanced caching rule (re-sending the same YouTube link returns the earlier zip uncharged). It also names the endpoint. This is real behavioral context beyond the structured fields.

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?

Front-loads the core action and outputs, then sources, then cost/latency/endpoint. Four tight sentences, no filler, every clause carries actionable information.

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?

Despite no output schema, the description explains the return value (zip containing MusicXML, staff PDF, numbered-notation PDF), the source options, the cost model and latency, so an agent has everything needed to invoke and interpret the call.

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 is 100%, so the schema already documents all four parameters. The description nonetheless clarifies what url may be (YouTube or mureka static-cos upload URL) and what song_id refers to, adding meaning in the selection between them beyond raw schema text.

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?

States a specific verb (transcribe) and resource (melody, chords, lyrics into sheet music) plus the concrete outputs (MusicXML, staff PDF, numbered-notation PDF). No sibling tool does anything similar, so it is trivially distinguishable from the rest of the mureka_* set.

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?

Enumerates the three valid source kinds (own song via song_id, YouTube link, or an MP3 already uploaded via mureka_upload_reference/mureka_upload_vocal) and thus routes the agent to the required prerequisites. It does not explicitly state when to prefer one source over another, but the context is clear.

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