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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, so the safety profile is covered. The description adds useful behavioural context beyond that: what each result contains (period of record, formats, keywords, description) and the upstream source (NOAA NCEI search service), which helps the agent anticipate the response shape when no output schema exists.

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 tightly written sentences: resource first, purpose second, provenance third. Front-loaded and free of padding, though the trailing attribution sentence is marginally dispensable.

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 enumerates what each dataset record includes, and the zero-required-parameter nature is handled by the schema's documented defaults. Adequate for a simple two-parameter discovery tool, with only the absence of named sibling alternatives as a small gap.

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 100% and both parameters (free-text search and limit) are well documented in the schema, including the default and max for limit. The description adds no syntax or semantic detail beyond the schema, so the baseline of 3 applies.

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 (browse/search) and resource (NOAA NCEI dataset catalogue) with concrete scope examples (climate, marine, satellite, radar, paleoclimate, storm). It distinguishes its role from data-pulling siblings by framing itself as discovery ('find which archive answers a question before pulling values'), though it does not name ncei_daily_summaries or ncei_station_search explicitly.

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?

Gives clear context for use — find the right archive before pulling values — which positions it as the discovery step ahead of the actual data tools. No explicit when-not or named alternatives, but the intent is unambiguous.

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