get_cameras_along_route

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

With no annotations, the description discloses the straight-line corridor behavior, perpendicular buffer, sorting by route_fraction, and return structure. It also mentions default buffer/limit values and the active_only filtering semantics.

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?

Well-structured with a summary, caveat, parameter details, and return section. Slightly redundant with the schema's parameter list, but each sentence contributes and the organization helps scanability.

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 7-parameter tool with no annotations and a moderate output schema, the description covers behavior, key constraints (straight-line vs driving), result ordering, and output fields. It is complete for an agent to select and invoke correctly.

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?

Adds meaning beyond the schema: WGS84 coordinates, buffer in meters perpendicular to the line, limit range 1–100, and active_only mapping to camera_class=open. Schema only provides names and defaults.

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?

Clearly states 'Get traffic cameras along a straight-line route between two points' – a specific verb and resource that distinguishes it from radius/nearest/list tools. The straight-line qualifier is explicit.

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?

Notes it mirrors the VanCam route view and explicitly states it uses a straight line, not a driving route polyline. This tells users when to avoid expecting driving-route corridors, though it doesn't name alternative tools directly.

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