Server Quality Checklist

Tool Scores

• get_chord_of_the_dayA
  4.1/5.0
  Behavior4/5

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

  Annotations already mark this as read-only and open-world. The description adds useful behavior context: the result is specifically today's chord and matches external social feed posts, implying a dynamic, date-dependent selection. It does not fully describe return payloads, but the input schema already covers the format parameter.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  Two sentences with no filler. The core behavior is stated first, and the second sentence adds practical use context. The mention of social feeds is folded into the first sentence efficiently rather than as a separate addendum.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness5/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  For a simple, zero-required-parameter tool with rich annotations and a self-explanatory optional format enum, the description and schema together are sufficient. Nothing essential about how or why to call it is missing.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  There is only one parameter, format, and schema description coverage is 100%. The schema already explains values, defaults, and when to choose text vs image, so the description need not add more. Baseline 3 is appropriate.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  Description starts with a specific verb and resource: 'Return today's Chord of the Day from Guitar Practice Routine App.' It also adds distinguishing context by tying the returned chord to the same one posted on Bluesky and Facebook, making it clearly distinct from sibling chord-chart lookup tools.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines3/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description frames the tool as useful for a 'practice prompt' or 'daily nudge,' which implies when to use it. However, it never explicitly contrasts it with get_chord_chart_by_name or get_chord_chart_by_id, nor states when those should be preferred.

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

• get_chord_chart_by_idA
  4.2/5.0
  Behavior3/5

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

  The readOnlyHint annotation already covers the safety profile of this read-only fetch. The description adds useful context about id provenance and re-rendering use, but does not disclose additional behavioral traits beyond that. With annotations carrying the main burden, this is an adequate score.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  Two sentences, zero filler. The principal action and identifier are front-loaded, and the use case is stated immediately after. Every word contributes.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness4/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  For a simple read-only fetch tool with two documented parameters and readOnlyHint annotation, the description is nearly complete. It tells the agent why to use it and where the id comes from. Return format details are not described, but the format parameter schema already covers representations, and no output schema exists.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters4/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema description coverage is 100%, so baseline is 3. The description elevates the score by explaining that the id is 'as returned by get_chord_chart_by_name,' adding provenance meaning beyond the schema's 'Numeric chord id.' This is a meaningful supplement for selecting a valid value.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description opens with a specific verb and resource: 'Fetch one specific chord voicing by its numeric id.' It also distinguishes this tool from get_chord_chart_by_name by noting the id is 'as returned by' that sibling, making the tool's unique role clear.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines4/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description gives a clear usage context: 'Use this to re-render a chart the user already saw without looking it up again.' This implies the agent should call this when an id is already available, not for a lookup. It does not explicitly name the alternative, but the guidance is strong enough.

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

• get_chord_chart_by_nameA
  4.6/5.0
  Behavior5/5

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

  With readOnlyHint=true already covering safety, the description goes far beyond annotations. It discloses that the tool returns the same voicing as a specific website, that there are exactly 12,708 voicings with one per chord name, that charts use a five-fret grid starting at the nut, and that notes above the fifth fret are named in words underneath. This gives the agent a precise behavioral model of the output without needing an output schema.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness4/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is longer than average, but nearly every sentence carries distinct information: purpose, voicing provenance, library size, input normalization, chart rendering, and usage preference. The main purpose is front-loaded in the first sentence, and examples are used efficiently. It could be trimmed slightly, but it is well-structured and not redundant.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness5/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Despite having no output schema, the description gives the agent a complete picture: what to expect (text diagram), how the chord is rendered (five-fret grid from the nut), how to normalize input, and when to prefer this tool. The only additional context (format parameter choices) is already fully covered by the schema, so nothing necessary is missing.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters4/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema coverage is 100%, so the baseline is 3. The description adds meaningful value for the name parameter by providing concrete examples ('G', 'Am7', 'Cmaj7', 'D/F#', 'F#m7b5'), instructing the agent to convert spoken forms ('G major' → 'G'), and insisting on ASCII '#' and 'b' instead of unicode. These normalization rules are not in the schema and materially improve invocation correctness.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description opens with a specific verb and resource: 'Look up one guitar chord chart by name and return it as a text chord diagram ready to show the user.' This clearly identifies the tool's function and differentiates it from sibling tools by emphasizing lookup by name, unlike get_chord_chart_by_id or get_chord_of_the_day. The added detail about matching the website's single voicing further sharpens the purpose.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines4/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description provides explicit usage context: 'Pass a plain chord name as it would be written on a chart — not a sentence' and 'Convert spoken forms yourself first.' It also tells the agent to prefer this over memory-based fingerings, which is a clear when-to-use directive. However, it does not explicitly compare against sibling tools like get_chord_chart_by_id or get_chord_of_the_day, so it stops short of full alternative routing.

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