road_traffic_situations

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

Annotations already set readOnlyHint=true and destructiveHint=false, indicating a safe read operation. The description adds behavioral details: data is updated live, cache TTL of 2 minutes, and data source (ASTRA VMZ-CH). 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 moderately long but well-structured with clear sections: purpose, data source, complement info, requirements, details, and return format. Every sentence adds value, though some redundancy exists (e.g., data source repeated).

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?

The tool has 3 input parameters (though nested) and an output schema. The description adequately covers the return structure but lacks parameter details. Given the complexity and that output schema exists, it is reasonably complete but could include parameter guidance.

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?

Context signals show schema description coverage is 0%, meaning the description does not explain the parameters. The description only lists return fields, not input parameters like 'limit', 'active_only', or 'filter_type'. With 0% coverage, the description should compensate but fails to do so.

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 starts with a specific verb 'Get' and resource 'current Swiss traffic events: accidents, roadworks, congestion.' It clearly states what the tool does and differentiates it from sibling 'road_find_sharing' by saying 'shows WHY a road is currently blocked.'

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 explicitly compares to 'road_find_sharing' to indicate when to use this tool: 'while road_find_sharing shows WHERE vehicles are available, this tool shows WHY a road is currently blocked.' It also mentions a prerequisite: 'REQUIRES: OPENTRANSPORTDATA_API_KEY environment variable.' However, it does not provide explicit when-not-to-use scenarios.

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