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

Annotations already declare this is a read-only, idempotent, non-open-world operation, so the safety profile is covered. The description adds real behavioral context beyond that: it warns that tab spacing conveys no note duration, which tells the agent the output timing is unspecified, and it scopes accepted input. It doesn't discuss output shape or error behavior.

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 short, front-loaded sentences with no filler; the core operation leads and the caveats follow. Every sentence carries a distinct piece of 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?

With no output schema, the description should do more to describe the returned data; it only says "sounding piano pitches" and notes the absence of duration. The unaddressed `capo` parameter and thin output description leave gaps for a 2-parameter conversion tool.

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 the description must carry the load. It does characterize the primary `tab` parameter as six-line ASCII tab text, but gives no syntax details, and the `capo` parameter (0–12, which shifts sounding pitches) is never mentioned at all — a meaningful semantic hole for a transposition-relevant tool.

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 (convert) and both resources (six-string ASCII guitar tab → sounding piano pitches). This is unambiguous and clearly distinct from the sibling tools (find_music_guides, spell_piano_chord, transpose_chords), none of which perform tab transcription.

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 GP files or audio uploads" sets clear input boundaries, telling the agent this is text-tab only, and the six-string/ASCII constraint implies when the tool applies. It stops short of naming an alternative for the excluded formats or stating prerequisites, 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.