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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and cacheability are covered. Beyond that, the description adds a genuinely important trait: 'Tab spacing does not specify note duration,' which tells the agent that timing/duration will not be derived and that output is pitch-only. That is real behavioral context an agent could not get from the annotations or schema.

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: the core transformation first, then the most consequential behavioral caveat, then input-scope exclusions. No filler, no restatement of the title, and each sentence carries distinct 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 say more about what comes back — pitch names with octaves? a list per string/position? — and 'sounding piano pitches' only gestures at it. The total omission of `capo`, a parameter that changes the output pitches, is a notable completeness gap for a two-parameter tool, though the duration caveat and input-format exclusions keep it at a minimum-viable level.

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 description coverage is 0%, so the description carries the full burden, and it largely does not meet it. The `capo` parameter — which directly transposes the resulting pitches and accepts 0–12 — is never mentioned in the description despite having no schema documentation, and the 20,000-character limit on `tab` is also absent. Only the 'six-string ASCII' phrasing loosely characterizes the `tab` input.

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?

Names a specific transformation with both endpoints: 'six-string ASCII guitar tab' in, 'sounding piano pitches' out. The input format and output domain are unambiguous, and none of the siblings (find_music_guides, spell_piano_chord, transpose_chords) overlap, so no explicit differentiation is needed. It stops short of 5 only because it never acknowledges the sibling set or its position among them.

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 description gives negative scoping — 'No GP files or audio uploads' — which usefully rules out input types an agent might otherwise try. However, it offers no positive when-to-use guidance and no routing to alternatives, so the agent must infer that this is the tool for any ASCII-tab-to-pitch conversion.

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