traffic

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

The description adds the behavioral context that it uses the 'Autobahn-API', which hints at data source limitations or update patterns. However, it does not detail any behavioral aspects beyond the annotation indications (readOnly, etc.). No contradictions 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?

The description is a single sentence with no wasted words. It front-loads the core purpose effectively. However, it could benefit from additional structure or details to improve clarity.

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 the absence of an output schema, 0% parameter coverage, and numerous sibling tools, the description is incomplete. It does not explain the output format, how to use the 'slug' parameter, or what to expect as return data. More context is needed for effective use.

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 schema defines one parameter 'slug' without description. Schema description coverage is 0%. The description does not explain the meaning of 'slug' (likely region identifier) or any constraints. Parameter semantics are completely absent.

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 specifies the resource: 'construction sites and traffic messages' and the source ('Autobahn-API'), clearly indicating it fetches traffic-related data. It does not explicitly state a verb like 'retrieve', but the context implies retrieval. It distinguishes from sibling tools like 'accidents' and 'road_events' by focusing on general traffic messages and construction sites.

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 lacks any guidance on when to use this tool versus alternatives. No explicit 'use this when' or 'use that instead' is provided. The sibling tools are not referenced, leaving the agent to infer without context.

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