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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuinely useful context beyond that: public-domain sourcing, weekly cadence, and the access model (free with X-ORKID-API-Key or $0.005 USDC per call via x402). It stops short of describing freshness/lag or rate limits.

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 tight sentences, with the resource defined first and operational facts second. The 'Params: limit' fragment is slightly redundant with the schema and misleadingly incomplete given that panel exists.

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 convey the return shape; it says net positions on a weekly cadence, which is adequate at a high level, but says nothing about row structure, units, or how the single panel choice affects results. Acceptable for a simple two-param read tool but not complete.

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 both limit and panel are already documented in the schema. The description only repeats 'Params: limit' and omits panel entirely, adding no meaning beyond the structured fields — 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?

Names a specific dataset (CFTC Commitment of Traders financial-futures positioning) and the exact content returned (weekly commercial/non-commercial net positions from the cot_positions panel). It implicitly separates itself from price-oriented siblings like sv_futures, though it never names them.

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?

There is no statement of when to use this versus sv_futures, sv_factors, or sv_macro, and no exclusions or prerequisites. The only guidance is the implicit 'COT positioning' framing, which an agent must infer from the name.

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