Server Quality Checklist

Tool Scores

• edit_diagramA
  4/5.0
  Behavior3/5

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

  With no annotations, the description carries the transparency burden. It discloses that the change is applied and that an updated share URL is returned, but it does not mention whether the original diagram is overwritten, whether changes are reversible, or any error conditions. This is adequate but leaves 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 two sentences with no redundant phrases. It front-loads the action and purpose, then provides a concrete example and return value, making every word earn its place.

  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, two-parameter tool with no output schema, the description covers the essential context: what it does, an example of the instruction format, and the return value. It could add prerequisites or caveats, but the information provided is sufficient for basic use.

  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 both parameters. The description adds an example instruction, but does not provide additional semantic detail beyond what the schema gives, meeting the baseline for full 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 starts with a specific verb+resource: 'Apply a plain-English change to a diagram previously created with generate_diagram.' It clearly distinguishes this from the sibling generate_diagram by focusing on editing existing diagrams, and includes a concrete example.

  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 phrase 'previously created with generate_diagram' gives a clear prerequisite for when to use this tool. However, it does not explicitly state exclusions (e.g., when not to use it) or alternative tools beyond the implicit contrast with generate_diagram.

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

• generate_diagramA
  4.2/5.0
  Behavior4/5

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

  With no annotations provided, the description conveys key behavioral aspects: it creates a diagram, accepts various source formats, and returns a URL plus diagram_id. It does not disclose potential side effects like resource consumption or rate limits, but for a generation tool, the core behavior is disclosed.

  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 compact and front-loaded. The first sentence states the primary action and input types; the second explains the output and follow-up capability. No unnecessary words or repetition.

  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?

  Given the absence of an output schema, the description appropriately explains what is returned (shareable URL and diagram_id). It covers input formats and hints at subsequent editing. It lacks error-handling or authentication details, but these are not critical for a generation tool and the description is fairly 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 schema already documents both parameters well. The description adds context about input types and the auto-detection default, but this largely reinforces what the enum descriptions already convey. No significant additional parameter semantics are needed.

  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 generates diagrams from natural language or source code, specifying the output (shareable URL + diagram_id) and hinting at the sibling tool for follow-up edits. It distinguishes itself well from edit_diagram.

  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 the input types (natural-language description or source code formats) and mentions that the returned diagram_id is for follow-up edits, implying when to use edit_diagram instead. However, it does not explicitly state when not to use this tool or provide direct alternative comparisons.

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