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

Beyond the readOnly/openWorld annotations it discloses the exact provenance (BLS series via FRED), the history window cap, the pricing model ($0.002 USDC per successful call), the payment rails (x402 on Base/Solana/Arc), and that failed calls are free. That is substantive operational context the annotations cannot convey.

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?

Two sentences, front-loaded with the data identity and the key disambiguation, followed by coverage and payment terms. Even the remark about the route name earns its place by explaining a potentially misleading tool name.

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, return-value detail is rightly omitted. The description supplies provenance, scope, disambiguation, and cost/payment behavior – everything an agent needs to call it correctly and understand the billing consequence.

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% and the month range (1–24, default 3) is already documented in the schema. The description's 'up to 24 months of history' restates that bound rather than adding format or behavioral detail, 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?

It names the exact BLS series (WPU0911), the source (FRED), the frequency (monthly), and explicitly disambiguates from the RISI NBSK benchmark that the route name implies. An agent can tell precisely what data this returns without opening the schema.

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 exclusion is explicit – 'not the RISI NBSK benchmark' – so an agent seeking the NBSK price knows to look elsewhere. It stops short of naming an alternative tool for that case, but no sibling in the list covers NBSK, so the guidance is effectively complete for this catalogue.

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