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

Annotations only declare readOnlyHint and openWorldHint, so the description adds real value: the x402 payment model ($0.002 USDC per successful call, Base/Solana/Arc, failed calls free), unit conventions ('as reported (metric tons, running bales…)') and output ordering ('top buyers first'). It stops short of stating auth setup or rate limits, but covers the costly-call behavior an agent needs.

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 payload (commodity scope, data fields, ordering, units, pricing) is front-loaded into one dense but well-ordered passage. It is long for a single sentence-chain, but nearly every clause carries decision-relevant information, so little is wasted.

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 schema coverage, the description needn't restate return values; it still usefully explains units, ordering and the paid-call model. The only meaningful gap is that no alternative USDA report tool is referenced, leaving comparison to the sibling list.

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 the schema already documents all five parameters including commodity codes, week format and limit bounds. The description adds only indirect hints ('next-year sales' gestures at marketYear, 'top buyers first' at limit ordering) rather than explicit parameter semantics, so the baseline of 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?

States a specific verb+resource: 'USDA weekly export sales report (FAS ESR)' and enumerates the data set (weekly exports, net new sales, outstanding sales, accumulated exports, commitments). An agent can tell it apart from energy_usda_wasde_crop_reports by content, but the description never names that sibling explicitly, so differentiation is implicit rather than stated.

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 scope ('for one week of the marketing year', 'US totals and every destination') implies when the tool applies, and the schema carries defaults for week/marketYear. However, there is no explicit when-to-use vs when-not guidance and no named alternative such as the WASDE crop report tool.

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