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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful context beyond that: data source, output composition, historical acceleration, authoritative citations, and per-call cost. It does not discuss data freshness or limitations, but for a read-only reporting tool that gap is modest.

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 front-loaded with the use case and then the return value, example, source, and price. It is longer than strictly necessary, with some credibility/promotional framing, but each sentence contributes useful context for selection and invocation.

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?

For a single optional-parameter read-only tool with no output schema, the description is thorough: it covers when to use it, what it returns, example data, historical context, source authority, and cost. An agent has enough information to decide whether to call it and what to expect back.

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?

There is one optional 'year' parameter with default 2023 and 0% schema description coverage. The description's example ('2023 — 28 events...') implies the year parameter selects the disaster year, but it never explicitly states that, nor does it explain valid ranges, whether other years are supported, or how the 10-year trend context changes with the parameter. This is adequate for the default case but leaves a clear interpretive gap.

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 ('NOAA's official annual billion-dollar disaster economics') and the exact metrics returned: event count, total losses, deaths, and 10-year trend context. It is clearly distinct from general climate benchmarks by naming the authoritative NOAA NCEI series and the specific disaster-loss scope.

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 description explicitly says 'Use when establishing the macroeconomic cost of climate risk' and lists concrete contexts: ESG reporting, reinsurance negotiations, infrastructure investment decisions, and SEC/TCFD disclosures. It does not name sibling alternatives or provide 'when not to use' exclusions, but the intended context is clear.

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