get_nearest_cameras

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

With no annotations, the description carries the full burden. It discloses behavioral traits such as nearest-neighbor search, the active_only filtering (camera_class=open), and the ordering by distance_meters. It does not mention auth or rate limits, but for a read-only query tool these are not critical gaps.

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 structured with purpose, usage, parameters, and return sections. Every sentence adds value; the front-loaded purpose and bullet-like parameter list make it easy to scan.

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?

Given the tool's simplicity, four parameters, and an output schema, the description covers all necessary context: when to use, what parameters mean, and what the response contains. The sibling tool names clarify the alternative spatial queries, making the tool complete within its context.

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?

All four parameters are explained beyond the schema: lat/lon as query point in WGS84, limit with range 1–100 and default 5, active_only with the meaning of filtering to camera_class=open. Schema coverage is 0%, so this description fully compensates.

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 'Get the nearest traffic cameras to a geographic point,' which clearly states the verb (get), resource (traffic cameras), and scope (nearest to a point). It distinguishes itself from siblings like 'get_cameras_by_radius' and 'get_cameras_along_route' by focusing on nearest-neighbor semantics.

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 explicitly says 'Use when the user asks for the closest camera(s) to a location,' providing a clear when-to-use context. It does not list exclusions or alternative tools, but the context is specific enough to guide selection among sibling tools.

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