chuk-mcp-geocoder

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 clearly describes what the tool returns (server capabilities including tool lists and guidance) and mentions the output_mode parameter, though it doesn't address rate limits, authentication needs, or error behavior.

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

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

The description is well-structured and front-loaded with the core purpose, followed by specific details about arguments and returns. Every sentence adds value with no redundant information, making it efficient and easy to parse.

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

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

For a single-parameter tool with no annotations or output schema, the description provides adequate context about what the tool does and what it returns. It could be more complete by addressing potential limitations or error cases, but covers the essentials given the tool's relatively simple nature.

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

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

The description adds meaningful context about the single parameter (output_mode with options 'json' or 'text'), which compensates for the 0% schema description coverage. While it doesn't elaborate on format differences or default behavior beyond what's implied, it provides essential guidance for parameter selection.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with specific verbs ('Get full server capabilities') and resources ('complete list of tools, Nominatim API details, and LLM-friendly usage guidance'). It distinguishes itself from sibling tools by focusing on server metadata rather than geocoding operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context by mentioning what information is returned, but doesn't explicitly state when to use this tool versus alternatives like 'geocoder_status' or other sibling tools. No explicit guidance on prerequisites or exclusions is provided.

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