Server Quality Checklist

Tool Scores

• list_providersA
  3.7/5.0
  Behavior3/5

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

  There are no annotations, so the description carries full burden. It mentions that providers without keys will error when called, which is a useful behavioral warning. However, it doesn't disclose potential side effects (though listing is read-only, it could be mistaken), nor does it explain implications of configuration status, but the warning is a positive.

  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, extremely concise, and front-loaded with the core action (list all providers) and output details. Every sentence provides value: the second clarifies error behavior. No redundancy or fluff.

  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 tool's simplicity (no parameters, no output schema, no annotations), the description covers key aspects: what it lists, the error condition. It lacks explicit mention of the exact return format or whether it includes provider IDs, but for a list tool, this is largely sufficient. A minor gap is not specifying if it returns configuration status as structured data or human-readable text.

  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?

  The tool has zero parameters, so there are no parameter semantics to explain. The description focuses on the output content (default models, configuration status), which is sufficient. With no parameters, a baseline of 4 is appropriate as the description adds meaning about the result.

  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 lists all registered vision model providers, including their default models and configuration status. It distinguishes itself from sibling tools (analyze/describe/ocr) which are image-related operations, though it doesn't explicitly compare.

  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 doesn't explicitly state when to use this tool vs alternatives, but the purpose is clear enough that an agent would know it's for listing providers, not image analysis. It conveys usage context implicitly by listing what it returns, but no explicit exclusions or alternative tool references.

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

• analyze_imageA
  4/5.0
  Behavior4/5

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

  With no annotations provided, the description carries the full burden of behavioral disclosure. It does a good job: it mentions the ability to handle 1-9 images, supports multiple formats (local path, URL, data URI, base64), and clarifies that order is preserved and images can be compared/diffed. This goes beyond what one might assume and helps the agent anticipate multi-image behavior. However, it does not mention any potential failure modes, rate limits, or other operational details that could be relevant, though these may not be necessary for this tool.

  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 exceptionally concise—two sentences that efficiently convey the core purpose, input capabilities, and typical use cases. It is front-loaded with the primary function and does not contain redundant or explanatory fluff. Every clause adds value, and the structure flows naturally from what it does to how it behaves with multiple inputs.

  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 tool with four parameters, no nested objects, and no output schema, the description covers the essential aspects: input types, count limits, ordering, and example use cases. It gives the agent enough to invoke the tool correctly for common scenarios. It does not explain when to prefer this over describe_image or ocr_image, which could be considered a completeness gap given those siblings exist, but the description still stands on its own as a complete usage guide for the tool itself.

  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 description coverage is 100%, and the schema itself already thoroughly explains the parameters, including the images format, the order-preservation nuance, and the default prompt behavior. The tool description adds little beyond what the schema states. For instance, the description's note about 'compare, diff, or combine' is a rephrasing of the schema's 'compare, diff, or combine' text. Since the schema covers this ground, the description meets the baseline but does not add substantial new meaning.

  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's purpose: 'Analyze one or more images with a vision model and return the text result.' It specifies a verb (analyze) and a resource (images), and indicates the output (text). However, it does not differentiate from the siblings describe_image and ocr_image, which likely serve overlapping purposes. For example, it does not explain how analyze_image is distinct from describe_image beyond the multi-image capability.

  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 clear context for when to use the tool, listing use cases such as 'reading screenshots, photos, charts, UI states, document pages, etc.' This gives an agent a good sense of appropriate scenarios. However, it does not explicitly mention alternatives or exclusions, such as 'use describe_image for single images' or 'use ocr_image for text extraction only,' so the guidance is strong but not exhaustive.

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

• ocr_imageA
  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 burden and does disclose meaningful behavior: preserving reading order and paragraph structure, accepting 1–9 images, and returning transcripts in the given order. It does not mention output format or error behavior, but the core read-only transcription behavior is well covered.

  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?

  Three short sentences with the core action front-loaded. Every sentence earns its place, and there is no redundancy or filler.

  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?

  The description covers purpose, input limits, ordering, and typical use cases, which is sufficient for an agent to select and invoke the tool. Since there is no output schema, a brief note on return format would improve completeness, but this is a minor gap for a simple OCR tool.

  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 reinforces image order and count, which the schema already documents, but adds no parameter-level meaning for model, language, or provider beyond what the schema provides.

  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 states a specific verb ('transcribe all text') and resource ('image(s)'), and adds output characteristics (reading order, paragraph structure). This clearly distinguishes it from sibling tools like analyze_image and describe_image.

  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?

  It gives concrete use cases (screenshots, scans, invoices, slides) but does not explicitly state when to choose this tool over analyze_image or describe_image, nor when not to use it. The differentiation is implied by the OCR action rather than stated.

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

• describe_imageA
  4.2/5.0
  Behavior3/5

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

  With no annotations, the description provides limited behavioral info. It states that it accepts 1–9 images and preserves order, which is useful, but does not mention side effects, authentication, rate limits, or error handling. Since it's a descriptive read operation, the risk is low, but transparency is incomplete.

  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 concise sentences convey the core function, parameter limits, and ordering behavior without fluff. The information is front-loaded and efficiently structured.

  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?

  There is no output schema, but the description implies text output via 'Describe the image content'. It covers the input constraints and purpose adequately. While it doesn't specify return format, that is not critical for a description task, and the context is sufficiently complete.

  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 baseline is 3. The description adds value by explaining the images parameter: 'Pass multiple images to compare, diff, or combine them (e.g. before/after pairs, several charts) — order matters.' This enriches understanding beyond the schema's generic descriptions.

  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 states a specific verb ('Describe') and resource ('image content') with explicit scope (subject, layout, text, details). It also distinguishes from siblings by noting it is 'Equivalent to analyze_image with the default description instruction', which clarifies its relationship to a similar tool.

  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 implies usage by mentioning equivalence to analyze_image, suggesting that custom instructions would require analyze_image. However, it does not explicitly state when to use this tool over ocr_image or list_providers, leaving some ambiguity. Still, the core use case is clear.

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