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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds a genuine behavioral caveat about archived imagery availability and source/freshness metadata, but the 'Units: ft, kt, s, F, mi; directions FROM' sentence appears to be boilerplate that does not describe this tool's output and borders on misleading for a webcam listing.

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?

It is short and the purpose is front-loaded, but the units/directions sentence looks like recycled boilerplate that does not earn its place for a webcam-listing tool and dilutes the two genuinely useful clauses.

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, the description usefully notes that results include source and freshness metadata and that archived imagery may be unavailable. However, it omits any coverage/limit or pagination behavior and any routing against the many sibling find_*/list_* tools, leaving gaps for an open-world discovery tool.

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 0% and the single nested query object (lat/lon/spot) is undocumented in the schema, so the description must carry the load. 'Near a spot or coordinate' does map the two input modes to those fields, adding real meaning, but gives no format, precedence (spot vs lat/lon) or bounds guidance.

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 (list coastal webcams) plus the locating input (a spot or coordinate), which separates it from siblings like get_camera_image or list_spots. It is clear but does not explicitly name or contrast itself with the closest sibling (get_camera_image), so it falls short of a 5.

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?

No when-to-use or when-not-to-use guidance is given, and no alternative is named. An agent cannot tell from the description whether this is the discovery step before get_camera_image or a substitute for it; the 'archived imagery may be unavailable' clause hints at a limitation but never says what to do instead.

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