APIbase

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

With no annotations provided, the description carries full behavioral disclosure burden. It successfully indicates the return type is a polygon and identifies the external data source (Geoapify/OSM), but omits rate limits, authentication requirements, polygon format (GeoJSON), and error handling for mutually exclusive parameters.

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?

Single dense sentence with zero waste. Front-loads the core concept (isochrone), immediately clarifies the technical term with a parenthetical explanation, and ends with data source attribution. Every clause earns its place.

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?

No output schema exists, so the description must hint at return values. It mentions 'polygon' which partially addresses this gap, but lacks specifics on coordinate system, polygon complexity, or accompanying metadata. Adequate for a 5-parameter tool with excellent schema coverage, but not comprehensive.

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 description coverage is 100%, so the schema fully documents all 5 parameters including constraints. The description adds conceptual grouping ('time or distance') that maps to the mutually exclusive parameters, but does not add syntax, units, or format details beyond what the schema already provides. Baseline 3 appropriate for high schema coverage.

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?

Description uses specific verb 'Get reachability area' and defines the resource clearly as an isochrone polygon. It distinguishes from sibling geo.navigation.route by emphasizing area-based reachability (polygon) rather than path-based routing. The data source attribution (Geoapify/OSM) further clarifies scope.

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?

No explicit when-to-use or when-not-to-use guidance is provided. While the description implies use cases (travel reachability analysis), it does not contrast with geo.navigation.route or specify prerequisites like requiring coordinates first. Usage is implied but not directive.

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