chuk-mcp-geocoder

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

With no annotations provided, the description carries full burden. It discloses key behavioral traits: the tool performs a lookup operation, returns specific data fields (display name, structured address, bounding box), and has configurable output modes. However, it doesn't mention rate limits, authentication requirements, or error handling for invalid coordinates.

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 efficiently structured with a clear purpose statement followed by a well-organized parameter section. Every sentence adds value: the first defines the operation, the second explains what it returns, and the parameter documentation provides essential usage details without redundancy.

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 5-parameter tool with no annotations and no output schema, the description provides good coverage of inputs and return values. It explains what data fields to expect (place name, address components, bounding box) and parameter behaviors. The main gap is lack of explicit error handling or performance characteristics.

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?

With 0% schema description coverage, the description fully compensates by providing detailed semantic explanations for all 5 parameters. It clarifies lat/lon ranges, zoom levels with concrete examples (18=building, 10=city), language format expectations, and output_mode options with defaults - adding significant value beyond the bare schema.

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 ('reverse geocode coordinates') and resources ('place name and address'), distinguishing it from siblings like 'geocode' (forward geocoding) and 'nearby_places' (multiple results). It precisely defines the transformation from coordinates to location information.

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 specifying it returns 'the nearest place' for given coordinates, which distinguishes it from 'batch_geocode' (multiple coordinates) and 'admin_boundaries' (administrative boundaries). However, it doesn't explicitly state when to use alternatives like 'geocode' for address-to-coordinate conversion.

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