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 genuinely useful context beyond that: unit conventions (ft, kt, s, F, mi), that directions are FROM, and the important negative guarantee 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 sentences, front-loaded with the resource identity, and no filler. The units line is dense and telegraphic but still earns its place for an observation tool.

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?

The description notes it returns data plus source/freshness metadata, which partly substitutes for the absent output schema, and it flags the source attribution model. What is missing is routing guidance against the crowded field of sibling observation tools, which is the main gap for a zero-required-parameter read 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% for a nested query object containing bbox and category, and the description offers nothing about their format, accepted values, or semantics (e.g., bbox coordinate order, what categories exist). Neither the schema nor the description compensates, leaving the agent to guess.

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?

Names a specific resource (SECOORA coastal sensor observations) drawn from a published agency dataset, which is more distinctive than the generic siblings like get_observations or get_wind. However, it never explicitly contrasts itself with those sibling tools, so the agent must infer the boundary rather than being told it.

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?

There is no when-to-use statement and no named alternative among the many overlapping observation siblings (get_observations, get_source_status, get_conditions). The line 'Empty reports do not establish safe conditions' is an interpretive caveat about results, not guidance on when to select this tool.

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