Server Quality Checklist

Tool Scores

• scrollC
  2.7/5.0
  Behavior2/5

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

  No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions scrolling 'up or down' but doesn't describe how much scrolling occurs (e.g., by pixels, viewport height), whether it's smooth or instant, or any side effects (e.g., page reloads, element visibility changes). For a tool with zero annotation coverage, this leaves significant gaps in understanding its 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, efficient sentence with zero waste. It is appropriately sized for a simple tool and front-loaded with the core action. Every word earns its place, making it easy to parse quickly.

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

  Completeness2/5

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

  Given the tool's simplicity (1 parameter, no output schema, no annotations), the description is incomplete. It lacks details on scrolling behavior (e.g., amount, smoothness), usage context, and how it integrates with sibling tools like 'navigate'. Without annotations or output schema, the description should provide more context to compensate, but it does not.

  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 input schema has 100% coverage with a clear description and enum for the 'direction' parameter. The description adds no additional meaning beyond what the schema provides, as it only restates 'up or down' without explaining parameter implications (e.g., default behavior, effect on page position). With high schema coverage, 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.

  Purpose3/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description states the action ('scroll') and target ('the page') but is vague about scope and mechanism. It doesn't specify whether this scrolls by a fixed amount, to a specific position, or continuously, nor does it distinguish from potential sibling actions like navigating to different pages. The purpose is understandable but lacks specificity.

  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?

  No guidance is provided on when to use this tool versus alternatives like 'navigate' or 'click'. The description implies usage for scrolling but doesn't specify contexts (e.g., after loading a page, to view content) or exclusions (e.g., not for horizontal scrolling). Without such details, the agent must infer usage from the tool name alone.

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

• clickC
  2.9/5.0
  Behavior2/5

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

  No annotations are provided, so the description carries the full burden. It mentions the label ID format but doesn't disclose behavioral traits such as what happens if the element isn't found, whether it waits for the element to be clickable, or any side effects like page navigation. This leaves significant gaps for a mutation 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 a single, efficient sentence that front-loads the core action and context. Every word earns its place, with no wasted information, making it highly concise and well-structured.

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

  Completeness2/5

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

  For a tool that performs a click action (implied mutation) with no annotations and no output schema, the description is incomplete. It lacks details on error handling, success conditions, or what the tool returns, which are critical for an AI agent to use it effectively.

  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 input schema has 100% description coverage, with the parameter 'label_id' well-documented in the schema. The description adds minimal value by referencing the screenshot context, but doesn't provide additional semantics beyond what the schema already states. Baseline 3 is appropriate given high schema coverage.

  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 action ('click on an element') and the target resource ('by its label ID'), with specific reference to how the label appears in screenshots. It doesn't explicitly differentiate from sibling tools like 'multi_click' or 'navigate', but the specificity of using label IDs makes the 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 Guidelines2/5

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

  No guidance is provided on when to use this tool versus alternatives like 'multi_click' for multiple clicks or 'navigate' for navigation actions. The description implies usage with labeled elements from screenshots but doesn't specify exclusions or prerequisites.

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

• screenshotB
  3.1/5.0
  Behavior2/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 states the tool takes a screenshot and labels elements, but doesn't explain what 'labeled elements' means, whether this requires specific permissions, how the output is formatted, or if there are any side effects like pausing the page. This leaves significant gaps for a tool that interacts with a page.

  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, efficient sentence that front-loads the core action ('Take a screenshot') and adds a key detail ('with labeled elements') without any wasted words. Every part of the sentence contributes directly to understanding the tool's purpose.

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

  Completeness2/5

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

  Given the complexity of interacting with a page (implied by sibling tools like 'click'), no annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects like how labeling works, output format, or error conditions, which are crucial for a screenshot tool in this context.

  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 input schema has 0 parameters with 100% coverage, so no parameters need documentation. The description adds value by specifying 'with labeled elements', which provides context beyond the empty schema, though it's minimal. Baseline for 0 parameters is 4, as the description compensates adequately.

  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 action ('Take a screenshot') and the target ('current page'), with the additional detail 'with labeled elements' specifying what distinguishes this screenshot. However, it doesn't explicitly differentiate from potential sibling tools like 'click' or 'navigate' that might also involve page interaction, so it's not a perfect 5.

  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 like 'click' or 'navigate', nor does it mention prerequisites such as needing a page to be loaded first. It implies usage by describing the action but lacks explicit context or exclusions.

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

• multi_clickB
  3.2/5.0
  Behavior2/5

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

  No annotations are provided, so the description carries the full burden. It mentions the action ('click') and context ('CAPTCHA, checkboxes'), but doesn't disclose behavioral traits like whether it requires specific permissions, how it handles errors, if it's synchronous/asynchronous, or what the visual/state impact is. This leaves significant gaps for a mutation 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 a single, efficient sentence that front-loads the core functionality ('Click multiple elements at once') and adds a brief, useful example context. There is no wasted verbiage, making it highly concise and well-structured.

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

  Completeness2/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 mutation tool with one parameter, the description is incomplete. It lacks details on behavioral aspects (e.g., side effects, error handling), return values, and explicit differentiation from siblings. For a tool that performs actions like clicking, this leaves too many unknowns for effective agent 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?

  The schema description coverage is 100%, with the parameter 'label_ids' fully documented in the schema. The description adds no additional parameter information beyond what the schema provides, such as format details or constraints. 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.

  Purpose4/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description clearly states the action ('click multiple elements at once') and the resource ('elements'), with a specific example use case ('CAPTCHA, checkboxes, etc.'). However, it doesn't explicitly differentiate from the sibling 'click' tool, which presumably clicks single elements.

  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 implies usage for batch operations like CAPTCHA or checkboxes, suggesting when it might be preferred over single clicks. But it doesn't explicitly state when to use this versus the 'click' sibling or other alternatives, nor does it provide exclusions or prerequisites.

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

• navigateB
  3.2/5.0
  Behavior2/5

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

  No annotations are provided, so the description carries full burden. It discloses the behavioral outcome (screenshot with labeled elements) but omits critical details: whether navigation is headless or visible, timeout or error handling, authentication needs, rate limits, or what 'labeled interactive elements' entails (e.g., bounding boxes, types). This leaves significant gaps for a tool with potential side effects.

  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, efficient sentence that front-loads the core action and outcome with zero waste. Every word earns its place, making it highly concise and well-structured for quick understanding.

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

  Completeness2/5

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

  Given no annotations and no output schema, the description is incomplete for a tool that performs navigation and returns a complex result (screenshot with labels). It lacks details on behavioral traits, error conditions, output format, or prerequisites, leaving the agent with insufficient context to use it effectively beyond basic invocation.

  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%, with the parameter 'url' fully documented in the schema. The description adds no additional meaning beyond implying navigation, which aligns with the schema. Baseline 3 is appropriate as the schema does the heavy lifting, but no extra context is provided.

  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 specific action ('navigate to a URL') and the outcome ('return a screenshot with labeled interactive elements'), distinguishing it from sibling tools like 'screenshot' (which likely captures without navigation) and 'click'/'type' (which interact with elements). It uses precise verbs and specifies the resource (URL) and result format.

  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 like 'screenshot' (which might capture without navigation) or 'click' (which might require prior navigation). It lacks explicit when/when-not instructions or named alternatives, offering only implied usage based on the action described.

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

• typeA
  3.5/5.0
  Behavior2/5

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

  With no annotations provided, the description carries full burden for behavioral disclosure. While it mentions the typing action, it doesn't disclose important behavioral traits like whether this simulates keyboard events, what happens if no focus position exists, potential rate limits, or error conditions. The description provides only basic functional information without deeper behavioral context.

  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, perfectly front-loaded sentence that communicates the core functionality without any wasted words. Every word earns its place, making it maximally efficient while still being complete for its length.

  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?

  For a 2-parameter tool with no annotations and no output schema, the description provides adequate basic functionality but lacks completeness. It doesn't explain what happens after typing, potential side effects, error scenarios, or return values. While concise, it leaves important contextual gaps for a tool that interacts with UI focus states.

  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 fully documents both parameters. The description doesn't add any parameter semantics beyond what's in the schema - it mentions typing text but doesn't elaborate on the 'text' parameter or 'submit' behavior. Baseline 3 is appropriate when the schema does all the parameter documentation work.

  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 specific action ('Type text') and target ('at the current focus position'), distinguishing it from sibling tools like click or navigate. It uses a precise verb+resource construction that leaves no ambiguity about what the tool does.

  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 implies usage context ('at the current focus position') suggesting this tool should be used when there's already an active text input field, but it doesn't explicitly state when to use it versus alternatives or provide any exclusion criteria. No sibling tool comparisons or explicit guidance are provided.

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