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), so the description earns credit for what it adds: 'Preserve source sample dates and unavailable states' warns that data may be missing and that sample dates matter, and 'Satellite clarity is a relative index, not measured dive visibility' prevents a serious misinterpretation. Return metadata ('source/freshness') is also disclosed.

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 short and front-loaded, leading with the purpose before caveats and the compressed 'Units: ft, kt, s, F, mi; directions FROM' clause. Nothing is redundant, though the unit string is dense enough to be slightly cryptic.

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 appropriately states what comes back ('data and source/freshness metadata'), supplies unit and direction conventions, and flags unavailable states and the relative nature of satellite clarity. Given the one-parameter, nested-object input, the main remaining gap is the spot identifier format.

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% for the single nested 'spot' string, so the description must carry the burden and largely does not. 'Verified spot' hints that the value must correspond to a known spot, but the required format (pattern, 1-120 chars) and whether it accepts an id versus a name are left unstated.

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 states a specific resource and scope: 'Local sargassum risk for a verified spot', which tells the agent exactly what is retrieved and that it is spot-scoped and local. It does not, however, differentiate itself from the very close sibling get_sargassum_outlook, leaving the agent to infer the local-vs-outlook distinction from names alone.

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 only usage signal is the phrase 'for a verified spot', which implies a precondition but does not explain what 'verified' means or how to satisfy it. With get_sargassum_outlook, get_algae_reports and get_red_tide as adjacent siblings, the description offers no when-to-use-this-vs-that guidance or exclusions.

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