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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, so the safety profile is covered. The description adds real context beyond that: provenance backing, latest/as-of values with prior-year changes and five-year comparisons, and an explicit scope limit that it is not a forecast or trading recommendation.

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?

Three sentences, front-loaded with the core action before examples and scope caveats; every sentence carries information. Slightly dense but no filler or repetition of the schema.

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?

No output schema exists, so the description must describe returns, and it does reasonably well (latest/as-of values, prior-year changes, five-year comparisons, provenance). Combined with full annotation coverage of the safety profile, an agent has enough to call it correctly, though the exact shape of the pack remains loosely specified.

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 crop, crop_class, as_of_year, and response_format are all documented in the schema itself. The description only echoes 'one major crop/class' and the 2019-2025 coverage, adding no syntax or aliasing detail beyond the schema, so 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?

States a specific verb (combine) and resource (hosted final annual USDA NASS national metrics) and names the deliverable (provenance-backed evidence pack). It does not, however, distinguish itself from the sibling usda_nass_crop_history / crop_trend / compare_crop_years tools, so an agent still has to infer why this pack beats a plain history call.

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?

Gives concrete triggering phrasings ('build a corn production evidence pack') and a composition hint ('as an agriculture leg to combine with weather, freight, fuel, or futures data'). It stops short of explicit when-not-to-use guidance or naming a sibling alternative for simpler single-metric lookups.

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