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

Beyond the readOnlyHint/openWorldHint annotations, it discloses the per-call cost ($0.006 USDC via x402) and the output shape, both material behavioral facts. It says less about the payment/auth flow itself, but the cost and mode constraints are the key operational details an agent needs.

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?

Three tight sentences, front-loaded with the core definition before use cases and pricing. Every clause carries information; only minor tightening is possible.

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 read-only geo tool with no output schema it sufficiently describes inputs, output (GeoJSON polygons), and cost. Gaps remain around lat/lon vs. near addressing and how ranges are passed, but the overall picture is complete enough to invoke correctly.

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 coverage is 57%, so several params (lat, lon, near) are undocumented in the schema; the description only partially compensates by adding 'truck' to the mode list and the 'up to 3 ranges' rule for ranges. It does not explain the lat/lon vs. near relationship or the minutes/km string format.

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?

It defines exactly what an isochrone is (reachable area from a place within N minutes/km), the supported travel modes, the 3-range cap, and the return format (GeoJSON polygons with km²). This clearly distinguishes it from siblings like route, route_matrix, places and geocode, which an agent could otherwise confuse it with.

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?

It names concrete scenarios — delivery zones, catchment areas, commute searches — which give a clear sense of when to reach for this tool. It stops short of explicitly contrasting itself with route/route_matrix (point-to-point routing vs. area coverage), so there is no 'when not to use' guidance.

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