neshan_isochrone

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

With no annotations, the description carries full burden. It discloses the return type (GeoJSON FeatureCollection), geometry control via 'polygon', metric property, and the ability to request both time and distance. It does not mention side effects or safety, but for a calculation tool, this is adequate.

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 two sentences, front-loaded with the purpose, and every word is informative. No redundant or irrelevant information.

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 (6 parameters, no output schema), the description covers key aspects: purpose, output format, and parameter interplay. It lacks details on coordinate system, error handling, or behavior of multiple features, but is largely sufficient for typical use.

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 baseline is 3. The description adds value by explaining output structure (FeatureCollection with geometry and properties) and how parameters interplay (both time/distance can be requested simultaneously), which goes beyond the schema's per-parameter descriptions.

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 purpose: 'Calculate the reachable area from a point within a given time or distance (isochrone).' It also describes the output format (GeoJSON FeatureCollection) and distinguishes from sibling tools by its specific functionality, though it does not explicitly contrast with 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?

The description implies that at least one of 'time' or 'distance' must be provided (from schema), and that both can be used simultaneously. However, it does not provide explicit guidance on when to choose this tool over siblings, nor any exclusions or prerequisite conditions.

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