Calculate EV Route

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

Annotations already mark the tool as read-only and open-world, so the safety profile is covered. The description adds useful behavioral detail: it delegates to ANWB EV route planning, requires specific EV inputs, and returns distance, duration, battery consumption, charging stops, and nearby charging stations. No contradiction with 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?

Every sentence earns its place: action, required inputs, outputs, and coordinate format with a pointer to find_locations. No filler or repetition of schema fields.

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?

For a tool with no output schema, the description gives enough about return values and prerequisites. It mentions the related find_locations tool, explains the locations serialization, and makes the tool's EV-specific scope clear. The remaining parameter details are already in the schema.

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?

The input schema has 100% description coverage, so the schema carries most parameter meaning. The description reinforces the locations format and prerequisite workflow, but does not add new details beyond the schema for parameters like carId, capacity, or stateOfCharge. Baseline 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 opens with a specific verb and resource: 'Calculate an electric vehicle route between two or more locations using ANWB EV route planning.' This clearly distinguishes it from general routing tools like calculate_route and also states the key outputs the agent can expect.

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 gives clear usage context: use for EV routes requiring car ID, battery capacity, and state of charge. It also explicitly instructs the agent to 'Use find_locations first to get coordinates for place names.' It does not explicitly name calculate_route as the non-EV alternative, but the EV-specific framing implies the distinction.

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