Server Quality Checklist

Tool Scores

• get_featureA
  4/5.0
  Behavior4/5

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

  With no annotations, the description carries the full burden and discloses important behaviors: each file body is preceded by a 'file: ..., ref: ...' header for source citation, and missing files are reported as missing rather than failing the call. This adds value beyond the schema.

  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?

  The description is three sentences, front-loaded with the primary directive, and every sentence contributes useful information (purpose, return format, error behavior). No wasted words.

  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 retrieval tool with no annotations and no output schema, the description covers purpose, usage, return format, and partial error behavior. It could clarify what happens if the entire folder is missing, but overall it is adequately complete.

  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?

  Schema coverage is 100%, so the baseline is 3. The description adds little beyond the schema—it echoes that slug is a feature folder name and repo is optional if GITHUB_REPO is set, but no new semantic details.

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

  Purpose4/5

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

  The description clearly states the tool returns three markdown files (product.md, tech.md, test-plan.md) for a feature folder, linking to feature-specific questions. It distinguishes from the sibling get_index by positioning itself as the feature-specific lookup, though it doesn't explicitly name the sibling.

  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?

  It explicitly says 'Call this for any feature-specific question,' giving a clear when-to-use context. It does not mention when not to use or name alternatives like get_index, but the context is sufficiently clear for an agent.

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

• get_indexA
  4.5/5.0
  Behavior4/5

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

  With no annotations, the description carries the full burden. It discloses that specs/INDEX.md is a derived rollup and not authoritative on its own, which is an important behavioral trait. It also clarifies the raw markdown format. However, it does not mention potential staleness or error behavior, which would add further transparency.

  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?

  The description is four sentences, each earning its place: usage guidance, core function, a caveat about authority, and a pointer to the sibling tool. No redundancy, well-organized.

  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 tool with one optional parameter and no output schema, the description covers purpose, usage, limitations (derived rollup), and follow-up actions. It fully equips the agent to decide when and how to use it.

  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?

  The schema already fully describes the repo parameter with a clear pattern and optionality context. The description does not add any new parameter-specific meaning, so baseline 3 is appropriate given 100% schema coverage.

  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 clearly states the tool returns the raw markdown of specs/INDEX.md for a repository, with a specific verb and resource. It also distinguishes itself from the sibling tool get_feature by positioning itself for cross-feature questions, making it unambiguous.

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

  Usage Guidelines5/5

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

  The description explicitly instructs to 'Call this first for any cross-feature question' and directs to 'follow up with get_feature' for specific feature details, providing clear when-to-use and alternative guidance.

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