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

Annotations only declare readOnlyHint=true. The description goes beyond that by disclosing the ordering ('newest first'), the upstream source, and an interpretive caveat that net figures can include hedges. It does not discuss pagination or rate limits, but the added semantic context is substantial for a read-only list tool.

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 that front-load the data source and returned fields, then append the caveat. Efficient, though the enum of example symbols (ES, GC, ZT) is somewhat redundant with the schema and could be trimmed.

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 names the return values (net speculative position, share of open interest, historical percentile) and notes ordering. Combined with full schema coverage, an agent has what it needs; only the hedging caveat's practical implication for interpretation is left loose.

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%, so limit, since, cursor and ticker are already documented in the schema, and the description's ticker note ('Not an equity ticker') largely duplicates the schema text. Baseline 3 applies since the schema does the heavy lifting and the description adds no new parameter semantics.

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 ('Weekly speculative positioning in FUTURES markets from the CFTC Commitments of Traders report') and enumerates the exact return fields, which sharply separates it from the equity-centric siblings (list_insider_trades, list_congress_trades). An agent can identify the domain 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?

It clearly scopes usage ('Covers futures symbols such as ES, GC, ZT, not individual stocks') and warns that net figures 'cannot be read as a directional view on their own.' That is strong context, but it never names a competing tool or an explicit when-to-use condition, so it stops short of full routing guidance.

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