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 effectively describes key traits: sequential processing to respect rate limits, fault tolerance ('individual failures don't abort the batch'), and retry guidance for failed queries. It also mentions external constraints (Nominatim rate limits and preference for simple names), adding valuable context beyond basic functionality.

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 appropriately sized and front-loaded with the core purpose. It uses bullet points and sections (Args, Returns, CRITICAL guidance) for structure, making it easy to scan. Some sentences could be tighter (e.g., the retry guidance is verbose), but overall, it efficiently conveys necessary information without waste.

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?

Given the tool's complexity (batch processing with fault tolerance and rate limits), no annotations, 0% schema coverage, and no output schema, the description is highly complete. It explains purpose, usage, parameters, returns, and critical behavioral guidance (retry logic). This provides all needed context for an AI agent to invoke the tool correctly and handle edge cases.

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?

Schema description coverage is 0%, so the description must compensate. It adds significant meaning for all parameters: 'queries' is explained as a JSON array of place names with an example, 'limit' as maximum results per query with a default, and 'output_mode' as options with a default. This covers semantics well, though it could clarify data types (e.g., 'queries' is a string in schema but described as JSON array).

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: 'Geocode multiple place names in one call.' It specifies the verb ('geocode'), resource ('place names'), and scope ('multiple'/'batch'), distinguishing it from sibling tools like 'geocode' (single) and other non-geocoding tools. 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.

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

The description provides clear context for when to use this tool: for batch processing of place names. It implies an alternative (the 'single geocode tool' for retrying failed queries) but does not explicitly state when to use one over the other or list other siblings like 'reverse_geocode'. The guidance is helpful but not exhaustive regarding all alternatives.

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