Traffic cameras

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

Annotations already declare readOnlyHint and openWorldHint, so the description is not responsible for safety signaling. It adds important behavioral context: results contain live-stream links rather than still images, and the user must open the link to watch, which prevents a common misuse.

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 compact and front-loads the resource and scope, with examples at the end. It is somewhat dense in a single sentence, but every clause carries useful information.

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 read-only lookup with a fully documented 7-parameter schema and no output schema, the description covers the essential scope, query modes, return nature (live-stream links), and practical examples. It could mention field-level return contents, but the critical behavioral caveat is present.

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 baseline is 3; the description earns extra credit by showing how key parameters pair in practice (network+keyword, network+lat/lon). It does not explain direction, radiusMeters, or limit, but the schema already documents those fully.

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?

States a specific resource (live traffic cameras) and scope (national freeways, provincial highways, or city roads), which distinguishes it from siblings such as traffic_live or traffic_events. The verb/resource pairing is obvious and immediately actionable.

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?

Explains the supported query modes (by road, place, or distance) and gives concrete examples for freeway+keyword and city+lat/lon usage. It does not explicitly compare against sibling tools, but the camera-specific scope and live-stream caveat provide clear context for when to use it.

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