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

Goes well beyond the readOnly/openWorld annotations by disclosing the cost model ($0.002 USDC per successful call), the payment rail (x402 on Base, Solana or Arc), that failed calls are free, and that each call downloads a ~1 MB CSV. These are precisely the operational facts an agent needs before invoking a paid, open-world tool.

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?

Front-loads what the tool returns before defaults and pricing; every sentence carries distinct information (scope, defaults, cost, payment rail, size). Slightly dense in a single run-on sentence but no wasted content.

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?

With an output schema present and full parameter coverage, the description only needs to cover scope, defaults and operational cost — all of which it does. Minor gap: it doesn't clarify whether multiple commodities can be retrieved in one call, though 'one commodity and region' implies not.

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 coverage is 100%, so all three parameters already carry examples and defaults (Corn, United States, YYYY-MM). The description adds the available attribute types (Production, Ending Stocks) but does not elaborate on parameter formats beyond what the schema states, so the baseline 3 applies.

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?

Names the specific source (USDA WASDE, official monthly report CSV) and the exact shape of each record: attribute, market year, value, unit, scoped to one commodity and region. This clearly distinguishes it from spot-price siblings like energy_cme_agri_spot_futures or energy_fao_food_price_index, though it never names those alternatives explicitly.

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?

Says it defaults to the latest available month and returns one commodity/region slice, which implies usage, but gives no explicit when-to-use versus the many other agricultural and food-price siblings. An agent must infer that this is for monthly supply/demand fundamentals rather than market prices.

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