Server Quality Checklist

Tool Scores

• get_balanceB
  3.1/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 burden. It mentions the return type ('Account balance information') but lacks details on authentication needs, rate limits, or what specific data is included in the balance. This is insufficient for a tool with no annotation coverage.

  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 brief and front-loaded with the main purpose, followed by a returns section. It avoids unnecessary words, though the returns section could be more specific to enhance clarity without adding bulk.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness3/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Given the tool has no parameters, annotations, but an output schema, the description is minimally adequate. It states the purpose and return type, but lacks context on usage, authentication, or detailed behavior, leaving gaps despite the output schema covering return values.

  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 0 parameters with 100% schema description coverage, so the schema fully documents the inputs. The description doesn't add parameter details, but with no parameters, this is acceptable, and it implies no input is needed, aligning with the schema.

  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 the action ('Get') and resource ('current account balance from Promotexter'), making the purpose understandable. However, it doesn't differentiate from the sibling tool 'send_sms' which is unrelated, so it doesn't reach the highest score of 5.

  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 or in what context. The description only states what it does, not when it should be used, leaving the agent without usage direction.

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

• send_smsA
  3.8/5.0
  Behavior2/5

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

  With no annotations provided, the description carries full burden for behavioral disclosure. While it mentions the action ('Send') and return type ('SMS send response with transaction details'), it lacks critical behavioral information such as authentication requirements, rate limits, error conditions, cost implications, or delivery guarantees. The description provides basic functional information but misses important operational context.

  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 perfectly structured and economical. It begins with a clear purpose statement, then provides organized parameter documentation in an Args/Returns format, with each sentence serving a specific 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.

  Completeness3/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Given that there's an output schema (which handles return values), the description covers the basic purpose and parameters well. However, for a mutation tool with no annotations, it should provide more behavioral context about authentication, costs, or operational constraints. The parameter documentation is excellent, but overall completeness is limited by the lack of behavioral transparency.

  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?

  With 0% schema description coverage, the description fully compensates by providing clear semantic meaning for all 3 parameters. It explains what 'to' represents (recipient mobile number with format requirement), what 'text' contains (message content with length limit), and the purpose of 'reference_id' (optional tracking). This adds significant value beyond the bare 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 specific action ('Send a single SMS message'), identifies the resource ('via Promotexter'), and distinguishes it from the only sibling tool 'get_balance' which is a read operation. The verb+resource combination is precise 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 usage context through the parameter documentation (e.g., 'must be valid mobile number format', 'maximum 1000 characters'), but doesn't explicitly state when to use this tool versus alternatives or any prerequisites. There's no explicit guidance on when-not-to-use or comparison with sibling tools.

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