Get Traffic Incidents

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

With readOnlyHint and openWorldHint annotations covering safety and world-data behavior, the description adds useful context by naming ANWB as the source, stating the data is current, and enumerating incident categories. Annotations are not contradicted.

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?

Three compact sentences: purpose, output contents, and filtering behavior. Each sentence contributes distinct information and the most important scope ('current traffic incidents on Dutch highways') is 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 simple read-only tool with no required parameters, the description tells an agent what will be returned (jams, closures, roadworks, speed camera locations) and how to filter. It does not specify the exact response shape, but no output schema exists and the listed categories provide enough for invoking the tool.

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 coverage is 100%, so the parameters are already fully documented. The description repeats the filter concepts ('Optionally filter by road and/or category') and examples like 'A1', but adds little semantic value beyond the schema.

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: 'Get current traffic incidents on Dutch highways from ANWB.' It enumerates the returned entity types (jams, closures, roadworks, speed cameras), which distinguishes it from summary/route/location siblings.

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 intended use is clear: call this when current Dutch highway incident data is needed, optionally narrowed by road and category. It does not explicitly name siblings or state when not to use them, but the context is unambiguous enough that no exclusion is needed.

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