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

Well beyond the readOnly/idempotent/openWorld annotations, it discloses that the return is an eYKON image URL rather than the frame or the operator's URL, that frames are timestamped by the operator rather than 'now', that only liveness-checked cameras appear, that absence is not evidence, and that attribution must be cited. This is rich disclosure an agent cannot get from the annotations or schema.

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?

Purpose and query modes are front-loaded, followed by behavioral caveats in a dense, information-bearing sequence. Each sentence carries a distinct fact, though a few (e.g., the frame timestamping clause) are more verbose than strictly necessary.

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?

With no output schema and no annotations covering return content, the description still specifies exactly what fields are returned (name, position, operator credit, image URL) plus safety semantics, making it complete for correct invocation and interpretation.

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 56%, and the description usefully groups parameters into three query modes (lat/lon with radius_km, bbox corners, aoi_id). However it never mentions the limit parameter and does not clarify the four bbox min/max corner params, so it only partially compensates for the coverage gap.

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 verb and resource ('Find LIVE public cameras') and immediately distinguishes itself from sibling tools like query_imagery and query_nightlights by naming the three query modes (bbox, point+radius_km, aoi_id) and the operator sources. An agent can tell exactly what this returns versus other geo-query siblings.

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 makes the three mutually-exclusive spatial query modes explicit and notes that only liveness-passed cameras are listed, which tells the agent how to frame queries. It stops short of naming a specific alternative tool to use when webcams aren't the right source, so no explicit when-not guidance is given.

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