Server Quality Checklist

Tool Scores

• convert_to_markdownA
  4.1/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 burden of behavioral disclosure. It explains that the tool runs automatically, converts files before they enter the context window, and reduces token usage—useful context. However, it does not explicitly state that the original file is not modified or address failure/edge-case behavior.

  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 a single, tightly packed sentence that conveys the trigger, input types, transformation, timing, and benefit. Every clause adds value with no repetition or filler.

  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?

  Given the simple one-parameter schema, the description fully explains what triggers the tool, what it does, when it occurs, and why it is useful. The lack of an output schema is acceptable because the transformation outcome (markdown in the context window) is clearly implied.

  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 single parameter 'file_path' is already well-documented in the schema. The description does not add parameter-specific detail beyond naming the input file, which meets the baseline for high schema coverage but does not exceed it.

  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 uses a specific verb ('converts') and explicitly lists the supported file types (PDF, DOCX, XLSX, CSV) and output format (markdown). It clearly distinguishes this tool's function as an automatic preprocessing hook, even in the absence of siblings.

  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 states that the tool is 'Called automatically by the PreToolUse hook when Claude Code reads a file,' which clearly communicates when it is triggered. It does not explicitly rule out manual invocation or name alternatives, but the automatic nature is clearly established.

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