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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world). The description goes beyond them by disclosing the return artifact (a starchild.music link), the fact that the original vocal is preserved, and the edge-case behavior of listing available styles when the requested style does not exist for that song.

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?

Three sentences, front-loaded with the action, then the return artifact, then the fallback path. No filler, though the long parenthetical example list makes the first sentence slightly heavy.

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 two-parameter read tool with no output schema, the description covers what is returned, the key preservation guarantee (original vocal), and the failure path. Only the sibling differentiation and auth/prerequisite context are absent.

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 baseline is 3, but the description enriches the 'style' parameter with additional concrete examples (Country, Acoustic Indie, Electro Rock, Latin Salsa, Piano Ballad Orchestral) and implies styles are song-specific, adding meaning the schema's terse 'e.g. country' does not.

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+resource ('Hear a Starchild song in a different production style') and clarifies the outcome (a link opening on starchild.music with the original vocal). However, it never distinguishes itself from siblings like transform_song or check_transform, which an agent could easily confuse with this one.

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 scenario of use is implied by the description (hearing an existing song in another style), and the fallback behavior when a style is unavailable is noted. But there is no explicit when-to-use guidance, no prerequisites, and no routing away from the similarly named transform_song/check_transform siblings.

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