clef

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, covering safety and determinism. The description adds that results are not file converters, clarifying output scope. However, it omits return format, pagination, and search behavior details like case sensitivity or ranking.

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?

The description is two sentences, front-loaded with the core purpose followed by a brief scope clarification. Every sentence earns its place, and there is no redundant or filler text.

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 search tool with no output schema and full annotation coverage, the description covers purpose and parameter meaning. However, it does not describe return values, result format, or search behavior nuances, leaving an agent to infer how results are presented. These gaps are minor but noticeable.

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?

The input schema has 0% description coverage for the single 'query' parameter, so the description must compensate. It explains that the query searches words in the title and description, giving clear meaning to the parameter. It could specify matching logic (e.g., AND/OR, exact phrase), but it sufficiently covers the parameter's purpose.

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?

The description states a specific verb ('Find') and resource ('Clef instructional guides') and specifies the search mechanism ('by words in the title and description'). It also clarifies scope by excluding file converters, though it does not explicitly differentiate from sibling tools. The purpose is clear and unambiguous.

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?

Usage is implied: use this tool to find instructional guides. The phrase 'Guides are not file converters' serves as a when-not condition but does not name alternatives or give explicit when-to-use guidance. No routing to sibling tools is provided, though the siblings serve different functions.

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

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description usefully adds scope exclusions (no rhythmic arrangement) and hints at the return shape, but says nothing about what 'supported chord' means or how invalid input behaves.

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?

Two short sentences, zero filler, with the core action front-loaded and the constraint immediately after. Nothing could be removed without losing meaning.

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?

The description is reasonably complete for a read-only, idempotent transformation with no output schema: it names the return values and rules out rhythmic output. It still leaves 'supported chord' undefined, which is the one thing an agent needs to call it correctly.

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% for both parameters, so the description must carry the load. It mentions 'octave' generically but never explains the octave range, default, or the accepted chord-symbol syntax (e.g., 'Cmaj7'), leaving the required 'symbol' parameter effectively undocumented.

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 ('spell') and resource ('chord') and names the output form (piano pitches with octave and MIDI values), so the transformation is unambiguous. It does not name any sibling tool, and the contrast is only implied through the rhythmic-arrangement disclaimer.

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 sentence 'This does not create a rhythmic arrangement' implicitly tells the agent when to prefer something else (e.g., tab_to_piano_notes) but never names that alternative or states the positive condition for choosing this tool. Usage is implied rather than directed.

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

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.

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world behavior, so safety is covered. The description adds real domain context (slash bass notes are handled; audio/lyrics/notation are out of scope), but says nothing about output format, enharmonic spelling behavior, or error handling for malformed chord strings.

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?

Two short sentences: the capability is front-loaded and the scope boundary follows immediately. No filler, no restatement of the tool name.

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 three-parameter tool with no output schema and zero schema description coverage, the definition is under-specified: an agent cannot learn what preferFlats does or what format the chords string expects from either the schema or the description. The scope note is helpful but does not close the parameter gap.

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% for all three parameters, so the description carries the full burden and does not meet it. It never explains the semitones direction/range or what preferFlats controls in the output, and 'chord symbols' is only loosely gestured at via the slash-bass mention.

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?

The description names a specific verb (transpose) and resource (chord symbols), then narrows domain further with the slash-bass-note case. The explicit negative scope ('Does not process audio, lyrics, or notation files') lets an agent separate this from transcription/notation siblings without opening a schema.

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?

Usage is implied by the domain exclusions, so an agent can infer this handles text chord symbols rather than audio or files. However, no sibling tool (spell_piano_chord, tab_to_piano_notes) is named as an alternative and no when-not condition is given beyond the input-format caveat.

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