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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds genuinely non-obvious behavior: catalog search is local title/slug filtering that does not guarantee a report per commodity, returned grades/weights/price units are raw source data rather than a sale price, and no automatic averaging or package conversion is performed. The only gap is that the idempotentHint=false implication (results can shift between calls) is never surfaced.

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 core constraints are front-loaded, which is good, but later sentences decay into near-tautology such as 'Follow its required fields and exact choices' and 'Supply units or modelVersion only when listed in inputSchema' — the latter is stated in the schema itself. There is also a typo ('last35days') and a dangling reference to 'the REST calculator field' that is never defined, adding noise rather than clarity.

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?

An output schema exists, so return values need no explanation, and the description covers the key operational facts for a read-only lookup: the two modes, the date-window and row limits, and the warning that values are unaveraged source data. Given the moderate complexity (nested oneOf, 3 top-level params), what remains missing is per-parameter meaning rather than tool-level behavior.

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 33%, so the description must compensate: it explains the 'inputs' wrapper and warns against passing an external REST calculator field, which are real clarifications that the schema's structure alone makes hard to infer. It adds the 7-day span and 50-row caps, though those partly duplicate the schema's own maximums and date descriptions, and it leaves reportId, commodity, mode and limit semantics largely unexplained.

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 states a specific verb and resource combination: 'Find USDA Market News reports, then retrieve an explicit report/date range', which conveys the two-stage catalog-then-report workflow. It does not name any sibling (e.g. buscalc_market_price_references or buscalc_bls_data_lookup) to distinguish itself from neighboring data lookups, but the agricultural-market-report scope is concrete enough that an agent can pick it out.

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?

There is implicit workflow guidance in 'Find ... then retrieve', so the description communicates that catalog search precedes report retrieval. However, it never states when to prefer this tool over the many sibling data lookups, nor any exclusions or prerequisites beyond the numeric constraints (7-day span, 35-day lookback, 50 rows).

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