get_map_clusters

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 disclosure. It adds the behavioral fact that results are clustered rather than raw webcams, but it does not describe clustering behavior, bounds handling, or how the response is optimized. This is useful but not rich.

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 with no filler. Every word carries purpose: resource, output shape, and intended display context. It does not repeat schema or annotation 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?

With a complete input schema, an output schema, and readOnly/openWorld annotations, the description covers most of what an agent needs to select and call the tool. Its only notable gap is lack of routing guidance to sibling webcam-list tools, but that gap is minor relative to the structured metadata provided.

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 description coverage is 100%, so parameter semantics are already fully documented. The description adds no parameter-level detail such as how zoom or include interacts with clustering, which meets but does not exceed the baseline.

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 uses a clear verb ('Get'), a specific resource ('webcam clusters'), and a context qualifier ('optimized for map display') that distinguishes this from individual-webcam or search siblings. It does not explicitly name or contrast any sibling, so it misses the strongest form of differentiation.

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?

'Optimized for map display' provides a concrete context for when this tool is appropriate, and 'clusters' implies aggregated output rather than single-webcam lookups. However, it gives no explicit when-not-to-use guidance or named alternatives such as get_nearby_webcams or get_webcams_by_location.

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