zbe.checkRoute

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

Without annotations, the description explains the core behavior: 'The API compares the vehicle's Euro emission class with each ZBE's minimum requirement. Returns which ZBEs are intersected and whether the vehicle is restricted from entering.' This adds useful context beyond the input schema, though it could mention error handling or rate limits.

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 composed of four efficient sentences: purpose, usage guidance, behavior, and return value. No redundant information; every sentence adds value.

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 no output schema, the description provides a high-level summary of returns ('which ZBEs are intersected and whether the vehicle is restricted'). It covers the essential aspects of the tool's functionality, though a bit more detail on the output structure would improve 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?

The input schema has 100% description coverage, so the baseline is 3. The description enhances meaning by explaining how the euroClass is used in comparison with ZBE requirements, and implies that weight and fuelType are relevant for the route check. This gives agents a better understanding of parameter roles.

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 verb 'check' and resource 'vehicle route intersects Low Emission Zones (ZBE/LEZ)', with explicit geographic scope 'Spain/Portugal'. It is distinct from sibling tools like zbe.getBadgeInfo or zbe.listPolygons, which focus on different aspects.

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?

Provides clear guidance: 'Use this when you need to know if a truck route passes through restricted urban areas.' While it does not explicitly list alternatives, the context is specific enough to differentiate from siblings.

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