Server Quality Checklist

Tool Scores

• demo_ordersA
  4/5.0
  Behavior4/5

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

  The description discloses that the tool is synthetic and side-effect-free ('Nothing is fetched and nothing is stored'), which is important behavioral context given no annotations. However, it does not mention determinism, randomness, or other potential behavioral nuances, but for a simple demo tool this is sufficient.

  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, front-loaded with the core purpose, and each sentence adds value. It avoids redundancy and is appropriately concise for the tool's simplicity.

  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 one-parameter tool with no output schema, the description adequately conveys the return type (JSON record array), synthetic status, and the demo purpose. It could still mention whether results are random or ordered, but the current level is sufficient for this low-complexity 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% for the single 'limit' parameter, which has its own min, max, default, and description. The tool description does not add parameter-specific meaning beyond the schema, so the baseline of 3 applies.

  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 uses a specific verb and resource: 'Return a synthetic order book as a JSON record array.' It clearly distinguishes this from the sibling tool demo_logs by stating it returns an order book, not logs. The phrase 'Nothing is fetched and nothing is stored' further clarifies its role as a synthetic demo.

  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 the tool is for viewing the shape of a record-style result ('so you can see what terse does to a record-shaped tool result'). It provides context for when to use it but does not explicitly compare with demo_logs or state when not to use it.

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

• demo_logsA
  4.3/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 behavioral burden. It discloses that the output is synthetic, plain-text, non-JSON, and a log tail, which conveys the nature and purpose. It does not mention side effects or permissions, but as a demo read-only tool, this is sufficient context. The description adds value beyond the bare schema.

  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, front-loaded with the core action, and every word earns its place. It efficiently contrasts with the sibling tool without unnecessary detail.

  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?

  This is a simple tool with one parameter, no output schema, and no annotations. The description sufficiently explains the return format (plain-text log tail), the synthetic nature, and the difference from demo_orders, making it complete for an agent to understand and invoke 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%: the single parameter 'lines' is fully described in the input schema, including default, range, and semantics. The tool description adds no additional parameter information, but since the schema already fully explains it, a 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 uses the specific verb 'Return' with the resource 'synthetic plain-text log tail', clearly stating what the tool does. It explicitly contrasts with demo_orders by noting the non-JSON format and the distinct audience ('terse's text tier'), distinguishing it from its sibling.

  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 gives clear usage context by contrasting with demo_orders: it returns plain-text logs, whereas demo_orders returns a record array. This implies when to use this tool (for text log output) versus the alternative, though it does not explicitly state 'use this when...' or exclude other cases.

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