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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description usefully discloses the time-stretch behavior (pitch changes, duration preserved), which is the non-obvious trait, but says nothing about output format, size limits, or acceptable input ranges.

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 short sentence with the key constraint front-loaded and no filler. Efficient, though its brevity is partly the cause of the missing parameter detail.

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 two-parameter audio transformation with no output schema and 0% schema coverage, the description leaves critical gaps: how semitones are interpreted, what form the audio file must take, and what the tool returns. An agent could not reliably call this without guessing.

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 0%, so both parameters are bare in the schema and the description must compensate — and it does not. The word 'semitones' never appears in the description, so the unit, sign convention (positive = up), and sensible bounds are entirely undocumented, as is the required base64 encoding of fileBase64.

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 ('Shift') and resource ('audio pitch') plus the key behavioral qualifier 'without altering speed', which implicitly separates it from the sibling audio_speed. It does not name that sibling explicitly, so differentiation is inferential rather than stated.

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?

No explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. The 'without altering speed' clause implies a contrast with audio_speed, but the agent must make that inference itself.

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