Server Quality Checklist

Tool Scores

• run_fixtureB
  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 must disclose behavior. It only states 'Run' without revealing side effects (e.g., executing tests, launching browsers), requirements, or output behavior. The agent cannot infer safety or operational impact.

  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?

  A single, front-loaded sentence conveying the core action and object with zero redundancy. Every word earns its place.

  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?

  With no annotations and no output schema, the description leaves significant gaps: no indication of what happens when the fixture runs, how results are returned, or how this tool relates to run_all_fixtures. The simple schema covers parameters, but operational context is missing.

  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 every parameter described. The description adds no new meaning beyond mapping 'specific test fixture' to fixtureName and 'deployment URL' to baseUrl. It meets the baseline for high schema coverage but doesn't enrich the semantics.

  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 uses a clear verb ('Run'), a specific resource ('a specific test fixture'), and target ('deployment URL'). It implies distinction from 'run_all_fixtures' by emphasizing 'specific', but does not explicitly name sibling tools, so it doesn't fully achieve the 5-level differentiation.

  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 use for a single fixture rather than all (suggested by 'specific'), but provides no explicit when-to-use vs. alternatives, no exclusions, and no context about prerequisites. Usage is inferable but not articulated.

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

• run_all_fixturesB
  3.4/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 behavioral disclosure burden. It only states the action (running fixtures) and provides no details about side effects, permissions, browser sessions, potential changes to the deployment, or the nature of the test execution. This is a significant gap for an execution 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, front-loaded sentence that immediately states the verb and object, with an optional modifier for tags. There is no redundant phrasing or filler; it is concise and appropriately sized.

  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 that there is no output schema and no annotations, the description should explain what happens when the tool runs (e.g., return values, exit codes, timeout behavior, or side effects). It only covers the action and filtering, leaving out operational context that an agent would need to reason about invocation and post-conditions.

  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 baseline is 3. The description adds minimal semantic context by associating tags with filtering and baseUrl with the deployment URL, but it does not provide additional syntax, format, or behavioral details beyond the schema.

  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: 'Run all test fixtures', identifies the target resource (fixtures), and specifies the context ('against a deployment URL'). It also notes optional tag filtering, which distinguishes it from the sibling 'run_fixture' tool by indicating plural coverage.

  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?

  Usage is implied: the description says it runs all fixtures or a tag-filtered subset, which suggests when to use it. However, it does not explicitly contrast with alternatives like 'run_fixture' (singular) or 'list_fixtures' (listing only), nor does it state 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.

• list_fixturesA
  3.8/5.0
  Behavior3/5

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

  With no annotations, the description carries full burden for behavioral disclosure. 'List' implies a read-only operation, but the description adds no further context about return format, filtering behavior, or scope limitations. It is not misleading but lacks depth for a tool with no 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?

  The description is a single sentence with no unnecessary words. It is appropriately sized for a simple list tool and gets straight to the point.

  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 list operation with one optional parameter and no output schema, the description is adequate. It clearly states what the tool does, and the schema covers the only parameter. Minor gap: it does not mention what the returned list contains (e.g., names, IDs), but this is likely inferred from 'fixtures'.

  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% (the only parameter 'tags' has a clear description). The tool description adds no information about the parameter, so it does not enhance what the schema already provides. 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 'List all available test fixtures' uses a specific verb ('List') and resource ('test fixtures'), clearly stating the tool's function. It distinguishes from sibling tools (run_fixture, run_all_fixtures) by focusing on listing rather than running.

  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 (list fixtures when you need to see what's available) but provides no explicit when-to-use or when-not-to-use guidance. It does not mention alternatives like run_fixture or run_all_fixtures, leaving the agent to infer based on sibling names.

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