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 behaviors: the tool resolves waypoints to coordinates, computes haversine distances, handles failures with retry logic, and supports output modes. It also includes critical retry guidance, though it could add more on error handling or performance aspects.

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 appropriately sized, with each sentence adding value. It starts with the core purpose, details the process, explains parameters and returns, and ends with critical retry guidance. There is no wasted text, and information is front-loaded for clarity.

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 (geocoding and distance computation), no annotations, and no output schema, the description is mostly complete. It covers purpose, parameters, returns, and retry behavior. However, it could be more explicit about error cases or output formats to fully compensate for the lack of structured data, slightly reducing the score.

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 significant meaning beyond the input schema, which has 0% coverage. It explains that 'waypoints' is a JSON array of place names in route order with an example, and 'output_mode' has options 'json' or 'text' with a default. This fully compensates for the schema's lack of descriptions, providing clear semantics for both parameters.

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 ('Geocode waypoints in order' and 'compute route distances') and distinguishes it from siblings like 'geocode' (single point) and 'distance_matrix' (all pairs). It explicitly mentions resolving waypoints to coordinates and computing haversine distances between consecutive points, which is precise and differentiates it from other routing tools.

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 (geocoding waypoints in order and computing route distances) and includes retry guidance for failed resolutions. However, it does not explicitly state when not to use it or name alternatives among siblings (e.g., 'distance_matrix' for all-pairs distances), which prevents a perfect score.

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