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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, so the description doesn't need to repeat these. The description does not contradict any annotations. The description adds valuable context about the output (ranked list, risk levels, commodity links), but since it takes no parameters (0 params), there's little to disclose about behavioral traits beyond what annotations cover.

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 focused two-sentence block. The first sentence succinctly describes the data (40 regions, ranked by risk), and the second sentence provides use-case guidance. Every sentence serves a purpose. It's not overly verbose, but could be slightly more front-loaded by placing the use-case first.

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?

Given the tool has zero parameters, annotations that fully cover its behavioral traits (read-only, idempotent), and an output schema (assumed present if not detailed), the description is complete. It tells the agent what the tool returns (ranked list with risk levels and commodities), and why to use it (identify climate stress and commodity exposure). There's no missing context for correct tool selection and invocation.

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?

With 0 parameters and 100% schema coverage, the description adds no parameter-specific details for completeness. However, the description compensates by clearly explaining what the output contains (regions ranked by risk, with commodities and risk levels, which implicitly tells the agent what to expect. For a parameterless tool, the score defaults to 4--the description effectively communicates output semantics beyond just the schema's void object.

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 a ranked list of ~40 global commodity production regions with climate risk scores and commodity exposure. It uses specific verbs ('ranked by,' 'shows,' 'identify') and the resource is well-defined as production regions with their risk levels and affected commodities. It also distinguishes from siblings like forecast.commodity_outlook (which focuses on commodities rather than regions) and forecast.portfolio_stress (portfolio-level stress).

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 states the tool's purpose: to identify geographic zones under climate stress and which commodities are most exposed. This implies it should be used for climate risk analysis on production regions, not for commodity-specific or portfolio-specific forecasts. However, it doesn't explicitly mention when NOT to use it or name alternative sibling tools for related purposes, which would improve clarity further.

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