cameras_for_entity

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

With no annotations, the description must carry the transparency burden alone; it does clearly indicate a read-only operation and discloses that the result includes the matching livetrafficcam.com page URL. However, it does not explain behavior for unknown slugs, pagination, or any further response conventions, so it only reaches adequate transparency.

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?

A single, front-loaded sentence that conveys purpose, scope, slug format, and one important output detail. It contains no filler and does not restate the parameter name.

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 one-parameter list tool with no output schema or annotations, the description covers the input contract and at least one key output element (the page URL). It could be more complete about other returned camera fields or error/empty behavior, but nothing essential for invoking it correctly is missing.

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 already fully documents entity_slug, so the baseline is 3, but the description adds meaning by specifying that the slug represents a pass, corridor, bridge, or tunnel and by providing two realistic examples (donner-pass, snoqualmie-pass) beyond the schema's single example.

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 opens with a specific verb ('List') and a precise resource ('traffic cameras for a named pass, corridor, bridge, or tunnel'), scoped by slug with concrete examples. This makes it distinct from siblings like cameras_by_state, which target states rather than entity slugs.

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 phrasing 'for a named pass, corridor, bridge, or tunnel by its slug' clearly communicates when to use this tool: when you have an entity slug. It does not explicitly name alternatives or when-not conditions, but the use case is strongly implied and unambiguous.

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