Server Quality Checklist

Tool Scores

• convert_to_webpA
  3.5/5.0
  Behavior3/5

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

  With no annotations provided, the description carries the full burden. It discloses key behavioral traits like batch processing, recursive directory scanning, and detailed reports, but lacks information on permissions, error handling, rate limits, or what the reports contain. It's adequate but has gaps.

  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 front-loaded with core functionality and efficiently uses two sentences with zero waste. Every phrase ('batch convert', 'customizable options', 'recursively scans', 'detailed conversion reports') adds value without redundancy.

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

  Completeness3/5

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

  Given no annotations, no output schema, and a 7-parameter tool with high schema coverage, the description is moderately complete. It covers the tool's scope and key behaviors but lacks details on outputs (reports), error cases, or advanced usage, leaving room for improvement.

  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 description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds no additional meaning beyond implying batch and recursive behavior, which is partially covered by parameters like 'src' and 'threads'. Baseline 3 is appropriate as the schema does the heavy lifting.

  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's purpose with specific verbs ('batch convert', 'recursively scans') and resources ('images (PNG, JPG, JPEG) to WebP format'), and distinguishes it by mentioning batch processing and directory scanning. No siblings exist, but it's still specific.

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

  Usage Guidelines2/5

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

  The description provides no guidance on when to use this tool versus alternatives (e.g., single-file conversion tools or other formats). It mentions 'customizable options' but doesn't specify scenarios or exclusions, leaving usage context implied at best.

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