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

Annotations already cover the safe-read profile (readOnly, idempotent, non-destructive), so the bar is lower, yet the description still adds real value: it states that recorded outputs and model reconstructions are identified separately, that coverage and gaps are preserved, that units are ft/kt/s/F/mi with directions FROM, and that source/freshness metadata is returned. The only thing missing is any hint of the record shape or pagination behavior.

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 units sentence is well-placed and front-loading the data scope is good, but the anti-fabrication warning is stated twice ("Never replace these with assistant-defined Calm/Moderate/Rough cutoffs" and "Never invent assistant-defined rough/calm thresholds"), and the self-referential "use get_chop_history" sentence earns no space.

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 no output schema, the description is responsible for signaling return content, and it does so by promising data plus source/freshness metadata and provenance flags. It is complete enough to call the tool correctly, though it omits the record granularity and whether timezone defaults apply to the range.

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 0% and the schema is a nested query object, so the description must compensate. It does partially: "verified spot ID" clarifies the required spot key and "up to 31 days" bounds the from/to range, but the nested query wrapper and the default/format semantics of the optional date-time fields are left entirely to the schema.

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 names a specific verb+resource (native 0-10 chop series over up to 31 days with daily mean/max, coverage and 7-day trends) and its scope is unambiguous. However, it never distinguishes itself from the closely related siblings get_chop or get_history, so an agent must infer the current-vs-historical split on its own.

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?

"For chop history or trends use get_chop_history with a verified spot ID" is essentially the tool's own name restated, so it adds little genuine routing guidance, and no alternative (get_chop for current conditions, get_history) is named. The precondition of a verified spot ID and the guardrail against substituting other series give partial context, so usage is implied rather than spelled out.

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