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

Annotations already mark this as read-only (readOnlyHint=true) and non-destructive. The description adds valuable behavioral context: the 4-hour cache, the ability to bypass it with the 'fresh' parameter, the specific return structure (signal, horizons, confidence, region breakdown, FRED price), and a disclaimer. This enriches the agent's understanding beyond what annotations provide. Score 4.

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 tightly written, with each sentence adding information. The first sentence states the core purpose ('Climate-driven price pressure outlook for a commodity'). The structure is clear and easy to parse. There is no wasted text or repetition. Score 5.

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?

The tool has a moderately complex output (multiple horizons, confidence, region breakdown, price reference), but an output schema exists. The description provides a high-level summary of the return structure, lists all supported commodities, mentions cache, and includes a disclaimer. It is adequate for an agent to understand what the tool returns and when to use it. Minor omissions: no mention of error handling or rate limits, but these are not critical for a read-only tool. Score 4.

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%, so the base is 3. The description does not add additional meaning to the parameters beyond what the schema already provides. The 'fresh' parameter's cache-bypass behavior is explained in the schema, and the description's mention of 'Cache: 4h' is redundant. The symbol enum is fully listed. Thus no extra value is added. Score 3.

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's function: 'Climate-driven price pressure outlook for a commodity.' It specifies the exact output format (BULLISH/BEARISH/NEUTRAL signals with horizons, confidence, region breakdown, FRED price) and lists the 11 supported commodities. However, it does not explicitly differentiate from sibling forecast tools (e.g., forecast.calendar, forecast.scenario), so a score of 4 is appropriate.

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 mentions the target audience ('institutional research teams evaluating commodity positions') and clarifies that signals reflect supply constraint risk, not a financial recommendation. But it does not provide explicit guidance on when to use this tool versus other forecast tools, nor does it state when not to use it (e.g., if a user needs financial advice or non-climate factors). This leaves room for ambiguity. Score 3.

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