driving_route

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states that the tool provides navigation info, distance, time, and cost estimates, but it does not explicitly disclose whether the operation is read-only, any prerequisites, or side effects. This is insufficient for a tool with no annotations.

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, concise sentence that is front-loaded with the primary purpose and key outputs. There is no wasted content or unnecessary details.

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 tool has 9 parameters and no output schema, yet the description only captures the basic function and outputs. It does not mention the tool's advanced capabilities such as waypoints, avoidance areas, vehicle type, or strategies, which are significant features. While the schema covers these, the description lacks a high-level overview of the tool's full scope.

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 baseline is 3. The description does not add meaning beyond the schema; it only refers to two points (origin and destination), while the schema already provides detailed descriptions for all parameters. No additional value is provided.

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 tool calculates driving routes between two points and lists the types of output (navigation info, distance, time, cost estimates). It is specific and distinguishes from sibling tools like walking_route and transit_route by explicitly saying '驾车' (driving).

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 usage for driving directions, as it mentions '驾车' (driving), but it does not explicitly state when to use it over alternatives like walking or transit. No exclusions or alternative tools are mentioned, so the guidance is only implied.

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