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

The readOnlyHint annotation already tells the agent this is a safe read operation, so the description carries less burden. It adds the REST endpoint reference but no other behavioral context such as rate limits, budget caps, or whether the result is a polygon. With annotations covering safety, this is an acceptable but not generous level of disclosure.

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?

Two short clauses with the core definition front-loaded, then the endpoint reference. No padding, no restatement of the title.

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?

There is no output schema, so the description could usefully say what is returned (e.g. a GeoJSON polygon or feature collection) and any budget/rate constraints. For a 7-parameter spatial tool, the definition is serviceable but omits return-shape detail the agent must guess at.

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 100%, so every parameter including lat, lon, mode, type, range and traffic is fully documented in the schema. The description adds no parameter syntax or format detail beyond that, which is the expected baseline when the schema does the heavy lifting.

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?

States a specific verb (compute) and resource (reachability isoline), then defines it precisely as 'the area reachable from a point within a time or distance budget'. This clearly differentiates it from the routing sibling and from the geocoding tools, without needing to name them.

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?

Usage is implied by the purpose statement (use this when you need an area reachable within a budget), but there is no explicit when-to-use guidance, no mention of alternatives such as geoapify_routing for point-to-point paths, and no prerequisites. Adequate but leaves the routing-vs-isoline choice to inference.

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