Server Quality Checklist

Tool Scores

• get_captureA
  4.3/5.0
  Behavior4/5

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

  With annotations already marking readOnlyHint=true, the description adds useful context about the return shape ('same shape as get_latest_capture') and the data source for ids. It does not disclose potential error behavior (e.g., not found) but is acceptable for a simple read operation.

  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 with no redundant information. Each clause serves a purpose: what it returns, how the output relates to other tools, and where to find ids.

  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 single-parameter retrieval tool with readOnly annotation and no output schema, the description is complete. It covers the input source, output shape, and relationship to sibling tools, leaving no critical gaps for an agent to invoke it correctly.

  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% with a clear description for the only parameter. The tool description adds 'Get ids from list_captures' which reinforces schema info, but does not add meaningful new semantics beyond what the schema already provides, matching the baseline for high 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?

  Description states a specific verb ('Returns') and resource ('one specific capture'), with scope also indicated ('by id'). It explicitly differentiates from siblings by mentioning get_latest_capture and list_captures, making its unique purpose clear.

  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?

  Provides clear usage context by referencing list_captures for obtaining ids and comparing its output shape to get_latest_capture. It implies when to use this tool (to fetch a known capture) but does not explicitly state when not to use alternatives, so a point off for lacking explicit exclusions.

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

• list_capturesA
  4.3/5.0
  Behavior4/5

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

  Beyond the readOnlyHint annotation, the description discloses ordering ('newest first'), preview behavior, and a performance trait ('cheap summary view'). It does not detail the exact content of previews or pagination behavior, but the added context goes beyond annotations.

  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 sentences, zero waste. The first sentence delivers the core purpose; the second adds context and differentiation. Information is front-loaded and every sentence earns its place.

  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 list tool with one parameter, an output schema, and a read-only annotation, the description covers the essential behavior, ordering, preview, and usage scenarios. There are no significant gaps.

  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 fully documents the only parameter ('limit') with description, default, and range. The description does not need to add parameter semantics; baseline 3 is appropriate.

  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 action ('Lists'), the resource ('captures'), and the scope ('user's recent'), plus ordering ('newest first') and content ('short text preview'). It also distinguishes itself from the sibling get_capture by framing it as 'the cheap summary view'.

  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?

  Provides clear usage context: 'Useful for finding an earlier capture when the user does not mean the newest one, or for working through several marked screens.' It explicitly names get_capture as an alternative but does not explicitly address get_latest_capture, leaving that distinction implied by context.

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

• get_capture_imageA
  4.5/5.0
  Behavior4/5

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

  Annotations already declare readOnlyHint true, so the description adds extra context: the image is downscaled and costs substantially more tokens than the structured form. This goes beyond the annotation's safety signal, though it doesn't mention potential errors or output format specifics.

  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 focused sentences: one for function, one for usage context, one for cost warning. Each sentence adds distinct value with no redundancy 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?

  For a simple two-parameter tool with no output schema, the description fully covers purpose, when to use it, and an important cost caveat. Annotations cover the read-only nature, making this complete in context.

  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 provides 100% coverage for both parameters (id and frame) with detailed descriptions. The tool description adds no additional parameter-level semantics, so the baseline score of 3 is appropriate.

  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 actual pixels of one frame as an image, distinguishing it from sibling tools like get_capture which returns structured data. It also specifies that the image is downscaled for model readability, making the purpose 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?

  Provides explicit use cases: visual questions that text and coordinates cannot settle, such as spacing, style, colour balance, or imagery without text. It also contrasts with the structured form of the same capture, implicitly indicating when not to use this tool.

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

• get_latest_captureA
  4.9/5.0
  Behavior5/5

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

  Annotations declare readOnlyHint=true, and the description adds substantial behavioral context by detailing the return structure (OCR elements, bounding boxes, colors, annotations, pointer associations) and explicitly stating that no image is returned. This goes well beyond the annotation and clarifies what consumers can expect.

  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 concise yet information-dense, with the primary action and return type front-loaded in the first sentence. The second sentence adds usage context and exclusions without redundancy.

  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 it has no output schema, the description enumerates the returned data elements in enough detail to set expectations, and it explicitly states what is not returned (no image) and where to find pixel data. This makes the tool's behavior complete for an agent.

  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 and schema coverage is 100%, so the baseline is 4. No parameter semantics need clarification, and the description correctly focuses on output and usage rather than inventing parameter details.

  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 newest SlimSnap capture as structured JSON with specific contents, and distinguishes itself from siblings by explicitly noting 'Returns no image' and emphasizing 'newest' versus a generic get_capture.

  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 provides explicit when-to-use guidance: 'Use this whenever the user refers to their screen, their last screenshot, "this", "here", or something they just marked.' It also explains when not to use it, directing users to the pixel tool for genuinely visual questions, and implicitly differentiates from list_captures and get_capture.

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