Server Quality Checklist

Tool Scores

• get_tidesB
  3.4/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. While it mentions what the tool returns ('Formatted string containing tide information and station details'), it lacks critical behavioral context such as rate limits, error conditions, authentication requirements, or whether this is a read-only operation. The description provides basic output format but misses important operational details.

  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 concise. It begins with a clear purpose statement, then provides organized sections for arguments and returns with specific formatting details. Every sentence adds value, and the information is front-loaded with the most important details first.

  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?

  For a 3-parameter tool with no annotations and no output schema, the description provides adequate but incomplete coverage. It explains parameters well and gives output format, but lacks behavioral context like error handling, rate limits, or authentication requirements. The absence of an output schema means the description should ideally provide more detail about the return structure beyond 'formatted string.'

  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?

  The description provides excellent parameter semantics despite 0% schema description coverage. It clearly explains each parameter's purpose: 'Float value representing the location's latitude/longitude' and 'Date string in YYYY-MM-DD format.' This fully compensates for the lack of schema descriptions and adds meaningful context beyond what the bare schema provides.

  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 tool's purpose: 'Get tide information for a specific location and date.' It uses a specific verb ('Get') and resource ('tide information'), and specifies the scope ('for a specific location and date'). However, with no sibling tools provided, there's no opportunity to differentiate from alternatives, preventing a perfect 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?

  The description provides no guidance on when to use this tool versus alternatives, prerequisites, or constraints. It simply states what the tool does without any context about appropriate usage scenarios. With no siblings listed, this omission is less critical but still represents a gap in guidance.

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