Server Quality Checklist

Tool Scores

• estimate_costC
  2.4/5.0
  Behavior1/5

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

  With no annotations, the description carries the full burden of behavioral disclosure, but it only states a high-level purpose. It does not disclose whether the operation is read-only, what the return format is, or any side effects, leaving the agent entirely uninformed about behavior.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness4/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single concise sentence with no filler words. It is appropriately short for a simple tool, though it errs on the side of under-specification, which is captured by other dimensions.

  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?

  The tool is simple (3 parameters, no output schema), but the description is still incomplete. It does not explain what the result of the cost estimation is, how units interact, or any expected outcome, making it inadequate for a tool with no annotations to support it.

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

  Parameters1/5

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

  Schema description coverage is 0%, and the description does not compensate by explaining any parameters. It does not mention material types, units, or quantity semantics, so the schema's enums and required fields are left without additional meaning.

  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 'Quick cost estimation for materials' clearly indicates the tool's purpose of estimating costs for materials, with 'cost estimation' as the verb-noun pairing. It distinguishes from social/messaging siblings, though it does not explicitly differentiate from the similar 'calculate_materials' sibling.

  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 usage guidelines are provided. There is no mention of when to use this tool versus alternatives like 'calculate_materials'. The word 'Quick' hints at a fast estimation context, but this is vague and not actionable.

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

• calculate_materialsC
  2.6/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 calculation function but reveals nothing about assumptions (e.g., units of measurement), whether the operation is read-only, what outputs are produced, or any limitations. This is a significant gap for a calculation tool.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness4/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single, front-loaded sentence with no filler words. It is appropriately concise, though it could benefit from a brief second clause or example to improve completeness without sacrificing readability.

  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 moderate complexity (nested dimensions object, enums, no annotations, no output schema), the description is notably incomplete. It fails to specify what types of materials are calculated, the expected output format, units, or any constraints, leaving the agent with insufficient information to invoke the tool reliably.

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

  Parameters1/5

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

  Schema description coverage is 0%, and the description does not compensate by explaining the meaning of 'structure' or 'dimensions' or their expected units. The schema property names are self-explanatory to a human, but the description adds no value over the structured fields, failing to meet the requirement for compensation at low 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 a specific action ('Calculate') and resource ('construction materials needed for basic structures'). It distinguishes from sibling 'estimate_cost' by focusing on materials rather than cost, though it could more explicitly enumerate the supported structure types.

  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 'estimate_cost'. It lacks explicit context about use cases or exclusions, leaving the agent to infer 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.

• send_group_messageB
  3.2/5.0
  Behavior2/5

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

  With no annotations, the description carries full responsibility for behavioral disclosure. It merely states the action without explaining side effects, failure modes, or what happens if the group does not exist. For a write operation, this is insufficient.

  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 clear sentence with no redundant words. It is concise and front-loaded, efficiently conveying the core 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 absence of annotations and output schema, the description is too sparse. It does not explain return values, success/failure behavior, or required prerequisites, leaving the agent with incomplete information for a tool that performs a mutation.

  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 both parameters described ('Message to send', 'Name of the WhatsApp group'). The description adds no additional 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 clearly states the action (send) and the target (WhatsApp group) with a specific verb and resource. It distinguishes from siblings like read_group_messages, which is about reading rather than sending.

  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. It does not mention that read_group_messages is for retrieving messages, nor any prerequisites or contexts where sending is appropriate.

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

• read_group_messagesA
  3.6/5.0
  Behavior3/5

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

  The word 'read' implies a non-destructive, read-only behavior, which is useful context. However, with no annotations, the description carries the full burden and does not disclose other behavioral traits like ordering of messages, rate limits, or whether any special permissions are required.

  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 directly states the purpose. No wasted words or redundant information.

  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 read tool with two parameters and no output schema, the description combined with the schema is adequate. It clearly conveys the tool's purpose and the limit parameter implies how 'recent' is quantified. Minor gaps like return format or ordering are not critical for this simplicity level.

  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?

  Both parameters are fully described in the schema (100% coverage), with groupName being self-explanatory and limit described as 'Number of recent messages to read'. The description adds no extra meaning beyond what the schema already provides.

  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 ('Read') and resource ('recent messages from WhatsApp group'). It distinguishes itself from the sibling tool 'send_group_message' by being a read operation, which is a natural differentiator.

  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. While the name and description imply it's for reading messages, it does not explicitly mention when to use it instead of send_group_message or other tools.

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