Server Quality Checklist

Tool Scores

• match_boardC
  2.6/5.0
  Behavior2/5

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

  The description reveals that the tool is optimized for zero-token (low-cost) pre-filtering and runs at Cloudflare Edge, giving some performance/latency context not inferable from the schema. However, it does not state whether the operation is read-only, what side effects might occur, what the return type is, or how it behaves on no match. With no annotations to fill the gap, the tool's safety and state-changing profile remain ambiguous.

  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 exactly one short sentence and wastes no words. It front-loads the key concept (zero-token pre-filtering) and only adds a useful deployment context ('Cloudflare Edge'). This is an ideal level of conciseness.

  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 a 4-parameter tool with a nested object and no output schema, the description leaves too much unsaid: no return type, no failure modes, no explanation of what a 'match' means, and no relationship to the sibling tool. The description might suffice for a trivial utility, but for an AI agent deciding whether to invoke this tool and how to interpret results, it is insufficient.

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

  Parameters2/5

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

  With 0% parameter description coverage in the schema, the description needed to clarify how 'domain', 'identity', 'intent_space', and 'similarity_threshold' relate to the match operation. Although the parameter names hint at a domain/identity against an intent space, the description does not explain their roles, accepted formats, or how similarity_threshold impacts results. The one-word description does not compensate for the missing schema documentation.

  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 provides a specific verb ('perform') and a noun phrase ('pre-filtering match check'), distinguishing it from a write operation, but it does not clarify what is being matched or what a 'match check' entails. It partially differentiates from the sibling 'post_board' by implying a read/check operation, but not explicitly. A clearer explanation of the input-output relationship would improve clarity.

  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 gives no guidance on when to use this tool versus 'post_board' or any alternative. No mention of use cases, exclusions, or preconditions such as 'use when you need to check membership' or 'for writes, see post_board'. The agent is left to guess when 'zero-token pre-filtering' is appropriate.

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

• post_boardB
  3.3/5.0
  Behavior2/5

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

  With no annotations, the description carries the full burden. It mentions a '24h deposit' and 'Cloudflare Edge' but does not clarify what that means (e.g., temporary storage, deletion after 24h, payment implications, or side effects). No mention of mutations, permissions, or reversibility.

  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 one concise sentence that front-loads the core action while adding the key constraint (24h deposit) and location (Cloudflare Edge). No wasted words.

  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 4 parameters (one nested object) and no output schema or annotations, the description provides insufficient context. It doesn't explain what 'deposit' means, the purpose of identity/intent_space, any auth requirements, or what happens after 24 hours. The description is too sparse for an agent to invoke safely without further inference.

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

  Parameters2/5

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

  Schema coverage is only 25% (payment_header has a description). The description does not explain domain, identity, or intent_space parameters, and only hints at 'deposit' which may relate to payment_header but not explicitly. The description fails to compensate for the low schema 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?

  The description clearly states the action ('Post a semantic intent board') and the target ('Cloudflare Edge'), distinguishing it from the sibling tool 'match_board' by its verb and resource. The purpose is specific and unambiguous.

  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 used for posting a board, but provides no explicit when-to-use or when-not-to-use guidance, nor does it reference alternative tools like match_board. It is clear but lacks explicit usage directions.

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