maps_routes

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

No annotations are present, so the description must fully disclose behavioral traits. It only mentions 'enhanced route planning with detailed navigation' without specifying key behaviors such as support for waypoints, traffic consideration, distance/duration outputs, or required authentication. This is insufficient for a routing tool.

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 sentence of 10 words, which is concise. However, it sacrifices informativeness for brevity; it could include more context without being verbose. Thus it is adequate but not exceptional.

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 absence of an output schema, the description should indicate return values (e.g., route duration, distance, steps). It does not. Additionally, it fails to explain how this tool differs from closely related siblings. The tool has 4 parameters and nested objects, yet the description offers minimal context.

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?

Input schema has 100% description coverage, so each parameter is documented. The description adds no further semantic context beyond 'detailed navigation', resulting in no additional value. Baseline score of 3 is appropriate.

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 uses a specific verb ('Get') and resource ('enhanced route planning'), clearly indicating the tool's purpose. However, it does not explicitly differentiate itself from the sibling tool 'maps_directions', which likely provides simpler routing.

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 like 'maps_directions'. There are no explicit when-to-use, when-not-to-use, or prerequisite conditions.

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