singapore_get_traffic_images

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so the bar is lower, and the description still adds real value by clarifying that image URLs are returned and never fetched by this server — a meaningful clarification given openWorldHint=true. It does not mention pagination behavior (limit/offset) or what happens when both camera_id and coordinates are supplied.

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 short sentences, front-loaded with the payload, and the final sentence (URLs returned, not fetched) prevents a costly misunderstanding. Nothing is redundant.

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?

An output schema exists so return shape needn't be explained, and annotations carry the safety profile. However, with seven parameters and near-zero schema coverage, the description leaves pagination and identifier filtering unexplained, which is a real gap for an agent constructing a call.

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?

Only date_time has schema documentation (14% coverage), so the description must compensate for six undocumented parameters, yet it only gestures at radius_km and the coordinate pair. limit, offset and camera_id — including how camera_id relates to the radius filter — receive no explanation in either place.

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 the specific resource and its payload: traffic camera image URLs, coordinates and timestamps, plus the optional radius filter. It is unambiguous what the tool returns, but it lacks an explicit verb (list/query) and never distinguishes itself from location-oriented siblings such as singapore_query_carpark_directory or singapore_query_lta.

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?

"Optional radius filter" implies a geo-scoped query, but there is no statement of when to choose this tool over the many other Singapore query tools, no prerequisite (e.g. that radius needs latitude/longitude), and no when-not guidance. An agent must infer usage entirely.

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