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

Annotations already declare readOnlyHint=true, and the description adds meaningful behavioral details: daily updates, data source provenance (NOAA NCEI, USGS, World Bank), and output composition. It does not disclose rate limits or error conditions, but the read-only safety profile is covered by annotations, so a 4 is appropriate.

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 a single substantive sentence plus a brief usage instruction and update frequency. It front-loads the return value and packs in essential context (data sources, output fields) without waste, though the parenthetical list makes it somewhat dense.

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 tool with one optional parameter and no output schema, the description is complete: it explains what is returned, when to use it, data sources, update cadence, and the optional history behavior is fully documented in the schema. No critical use-case or output information is missing.

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?

The only parameter 'days' has 100% schema description coverage, including its optional nature, history mode, and Gold tier requirement. The main description does not mention the parameter, but the schema fully explains it, so the baseline of 3 is appropriate with no added value needed.

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 uses a specific verb ('Returns') and a well-defined resource ('0-100 climate-adaptation capex priority score'), plus lists output fields (score, trend, confidence, top_drivers) and data sources. It clearly distinguishes this tool from generic siblings by domain and use case, and the 'Call when' section reinforces purpose.

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?

Explicit 'Call when' guidance is provided for physical climate risk, facility resilience, flood/heat exposure, adaptation ROI, and capital allocation timing. It lacks explicit statements of when NOT to use or named alternative tools, so it falls just short of a 5.

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