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

Annotations already declare readOnly/openWorld/non-destructive, so the bar is low, and the description adds real value: the data is 'stored' and 'weekly reported positions lag trading,' disclosing staleness. It also notes TFF and disaggregated categories 'remain distinct,' a nuance not in the annotations.

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?

Front-loaded with verb+resource, then progressive detail on scope, contents, and caveats. Dense but every sentence carries information; no wasted filler.

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 usefully describes return contents ('dated category long/short/net contract counts and open interest') and limits. Combined with the latency and category caveats, it is close to sufficient for correct invocation.

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 0%, so the description must carry the load; it does so reasonably by enumerating all four contract enum values and signaling the count nature of reports via 'up to eight stored reports.' It still omits the default value and what the count selects (e.g., most recent).

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 and resource (read stored CFTC futures-only reports) and enumerates the four supported contracts with their meanings. It distinguishes itself from sibling tools by scope, but never names an alternative sibling to route against.

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?

Provides clear exclusions — 'no wallet identities, real-time flows, options chain or stock shares' — which effectively tell the agent when this tool is not the right choice. It does not, however, name which sibling to use instead for those cases.

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