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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds useful context by naming sources (FEMA NFIP, NGFS scenarios) and disclosing the $0.02 USDC per call cost. It does not describe return format, coverage limitations, or data freshness, but the annotations cover the core safety profile.

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 compact and front-loaded with the main purpose, followed by useful context: sources, audience, and price. Every clause earns its place, though the dash-heavy structure makes it slightly fragmentary.

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 simple read-only tool with three optional enum parameters, the description covers purpose, sources, audience, and cost. It is missing guidance on parameter semantics and differentiation from nearby climate/ESG tools, which leaves some selection and invocation ambiguity.

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%, so the description must compensate for the three enum parameters. It partly maps to risk_type by naming physical and transition risks, but it does not explain the region or property_type parameters at all, nor how they affect results.

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 clearly states the tool provides climate financial risk benchmarks and enumerates the covered risk categories (physical, transition) and lender implications. It is specific about the resource, though it does not explicitly distinguish itself from siblings like get_climate_risk_score or get_esg_benchmark.

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?

It offers context by targeting 'ESG and risk agents' and cites data sources, which implies an intended use case. However, it never states when to use this tool instead of alternatives such as get_climate_risk_score, get_noaa_disaster_economics, or get_esg_benchmark.

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