calculate_route

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

The description does not address the destructiveHint annotation, which suggests side effects. 'Calculate' implies a read-only computation, but the tool may modify state. No explanation of what gets destroyed or other behavioral traits is given.

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 a single, clear sentence with no redundant words. It is front-loaded with the core purpose, though it could be expanded to include output hints without losing conciseness.

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?

The description lacks information about the return value (e.g., does it return geometry, duration, distance?) and does not clarify the destructive hint. Given no output schema, these omissions reduce completeness.

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?

All parameters are described in the input schema with clear names and types. The description adds no extra meaning beyond 'driving route', so it meets the baseline for full 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?

The description clearly states 'Calculate a driving route between two points', specifying the action and resource. It distinguishes from sibling tools like geocode or find_nearest_stations, which are about location data and stations rather than route calculation.

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 guidance is provided on when to use this tool versus alternatives. For instance, it could mention that for station-specific queries, sibling tools like find_route_stations are appropriate, but it does not.

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