sg_traffic_incidents

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

With no annotations, the description carries the burden of behavioral disclosure. It mentions the requirement of 'SG_LTA_KEY', which is a useful prerequisite, but it does not disclose response format, error behavior, rate limits, or data freshness details. The added context about the API key is valuable but incomplete for a full behavioral picture.

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 two concise sentences, immediately front-loading the core purpose and the API key requirement. Every word earns its place, with no redundancy or filler.

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 no-parameter tool, the description gives the essential purpose and a prerequisite, but it omits any information about the output structure, possible errors, or limitations. Without an output schema, the agent is left unaware of what the response looks like, making the description adequate but not fully complete.

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 tool has zero parameters, and the input schema is an empty object with 100% coverage. Since there are no parameters to describe, the description does not need to add parameter semantics. The baseline score of 4 applies here, and the description does not detract from it.

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 tool's function with a specific verb and resource: 'Get current traffic incidents on Singapore roads'. It distinguishes itself from sibling tools like sg_traffic_images by explicitly focusing on incidents rather than images or other 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?

The description implies usage for retrieving current traffic incidents but does not provide explicit guidance on when to use this tool versus alternatives. No exclusions or alternative tool mentions are present, so the usage context is only inferred from the purpose.

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