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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), and the description adds genuinely new context: units (ft, kt, s, F, mi), direction convention (FROM), the caveat that satellite clarity is a relative index rather than measured visibility, and the presence of source/freshness metadata. That is useful behavioral detail beyond structured fields.

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?

Front-loaded with the purpose, then compact unit/convention notes in three short sentences with no padding. The satellite-clarity sentence is slightly tangential for a surf zone forecast and reads like boilerplate, which keeps it from a 5.

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?

No output schema exists, and the description tells the agent it returns 'data and source/freshness metadata' without indicating what surf data appears (wave height, period, wind, rip risk), so the agent can invoke but not predict the payload. The units and direction conventions partially compensate.

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%, so the description must carry the parameter burden, but with one nested query.spot object the only added meaning is 'verified spot'. It does not say whether spot expects a display name, an ID, or a slug (the schema only shows a character pattern), leaving an agent to guess the accepted format.

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 (NWS surf zone forecast) plus the scoping condition (a verified spot), which an agent can distinguish from generic siblings like get_waves or get_forecast. It stops short of naming a sibling as the alternative, so 4 rather than 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?

'For a verified spot' implies a prerequisite (the spot must already exist, e.g. from get_spot/list_spots) and 'Preserve source sample dates and unavailable states' guides handling of partial results. However, it never says when to prefer this over get_forecast, get_waves, or get_rip_risk, so guidance is implied rather than explicit.

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