Server Quality Checklist

Tool Scores

• get_mock_api_statusA
  4.7/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 states the tool checks running status, port, and collections with item counts, implying a read-only inspection. It does not explicitly say it has no side effects or how errors are handled, but for a status check this is a reasonable level of disclosure. The description adds useful behavioral context beyond the bare tool name.

  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, both purposeful. The first sentence defines what the tool does, and the second gives usage context. There is no filler, and the primary function is front-loaded. It is concise without sacrificing clarity.

  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 the tool's low complexity (no parameters, no output schema, single sibling), the description is complete. It explains the purpose, the information returned, and the appropriate usage context. Nothing an agent needs to decide whether to call this tool is missing.

  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 the input schema is empty and schema coverage is trivially 100%. Per the rubric, a zero-parameter tool receives a baseline of 4. The description does not need to elaborate on parameters, and it does not, which 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's action: 'Checks whether the local mock API is currently running, on which port, and lists its collections with item counts.' It names a specific resource (mock API) and the information it returns, distinguishing it from the sibling setup_mock_api which would be for starting the server rather than inspecting its state.

  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?

  Explicit usage guidance is provided: 'Use this before assuming setup_mock_api needs to be called, or to confirm the server an Artifact is calling is actually up.' This tells the agent when to invoke this tool and frames it as a check before potentially calling the sibling, giving clear decision context.

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

• setup_mock_apiA
  5/5.0
  Behavior5/5

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

  With no annotations, the description carries full behavioral burden, and it succeeds: it discloses disk persistence to sandbox_db.json, idempotent behavior for existing collections, supported HTTP methods, and CORS support. These are exactly the side effects and runtime traits an agent needs to predict tool 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?

  Every sentence earns its place: purpose and motivation, resource definition, persistence semantics, and a precondition. Information is front-loaded with the verbs 'Starts (or reconfigures)' and critical behavior follows immediately. No filler or repetition.

  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?

  The description covers purpose, input shape, endpoint behavior, persistence, reconfiguration semantics, and the sibling tool check. Even without an output schema or annotations, an agent has enough to decide when to call it and how to construct a correct request.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters5/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Although the schema covers both parameters, the description adds essential meaning: schema keys become collections at /api/<key>, items get auto-generated IDs if missing, and the server exposes full CRUD. This goes beyond the schema by explaining how inputs map to runtime resources and endpoints.

  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?

  States a specific verb+resource: starts/reconfigures a local persistent REST API with CORS support. Clearly distinguishes itself from the sibling get_mock_api_status by naming it as the check step. The description leaves no ambiguity about what the tool accomplishes.

  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?

  Explicitly tells the agent to call get_mock_api_status before invoking this tool to avoid duplicate setup. It also explains the motivating scenario (state persistence across Artifact refreshes). This provides clear when-to-use guidance and names the relevant alternative.

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