Get Traffic Summary

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

Beyond the readOnlyHint and openWorldHint annotations, the description adds that the result is compact/aggregated, scoped to all highways, and composed of total counts rather than detailed incident records. It does not address freshness or potential limitations, but the annotations already cover the safety profile.

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?

A single, well-structured sentence delivers the purpose, scope, and output composition without any redundant filler. Information is efficiently front-loaded.

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 zero-parameter, read-only summary tool, the description is complete: it names what counts are returned, the geographic scope, and the temporal nature. No output schema exists, but the return content is described explicitly.

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 zero parameters, so there is no parameter documentation burden. The description reinforces that the tool takes no arguments by describing an all-highways aggregate result.

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 names a specific action ('Get') and resource ('compact summary of current traffic conditions on Dutch highways'), and enumerates the exact outputs (counts of jams, closures, roadworks, radars). This clearly separates it from sibling tools like get_traffic_incidents, which would provide more granular incident data.

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?

It provides clear context: use this tool when you need a high-level numeric snapshot across all Dutch highways. It does not explicitly state when not to use it or direct the agent to an alternative for detailed incident-level traffic information.

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