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

Annotations already declare the read-only, idempotent, non-destructive, open-world profile, so the safety story is covered. The description adds real value beyond them: it discloses that returns include source/freshness metadata, states the units and 'directions FROM' convention, and warns that empty reports do not imply safe conditions.

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?

Three short, front-loaded lines with no padding, and the dataset scope leads. The units line reads like a generic boilerplate blob (including kt, s, mi) whose relevance to a coral heat report is unclear, which costs a point.

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 does state the return shape ('data and source/freshness metadata') and a key caveat, which is the minimum viable for a zero-required-param read tool. However, the nested query object is left wholly unexplained, leaving a real gap for an agent trying to filter results.

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 (bbox, category) is entirely undocumented. The description supplies units (ft, kt, s, F, mi) but nothing about what bbox or category accept or how they scope the query, so the parameter burden is not met.

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+resource: 'Coral heat stress and bleaching outlook from the published agency dataset'. The subject matter is distinctive among siblings (get_water_temperature, get_reefs, get_sargassum_outlook), so an agent can pick it out, though no sibling is named as an explicit contrast.

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 guidance or alternatives are given. The only guidance-like sentence, 'Empty reports do not establish safe conditions', is an interpretation caveat rather than a selection rule, and nothing tells the agent when to prefer this over get_water_temperature or get_reefs.

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