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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: a fixed page size of 100 markets with offset paging, and access-tier behavior where Premium/Data API keys unlock both CFTC variants while anonymous and free users get only each report's default variant. It doesn't clarify what happens if a restricted user requests a non-default variant, but the disclosure goes well beyond 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 the core identity ('the latest Legacy COT report of every market') followed by page size, contents, filtering, and access tiers. The trailing account-tier clause is dense and slightly run-on, but every element carries information an agent would otherwise lack.

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 does the right work by naming the returned measures and the 100-market page size, and it covers auth tiers, which are essential for predicting failures. The main remaining hole is sibling disambiguation between this tool and get_latest_positions, which an agent needs in order to choose correctly.

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 all three parameters are fully documented in the schema, which sets the baseline at 3. The description reinforces meaning — offset as the next-page mechanism, category as a filter, variant as tier-gated — but adds no syntax or edge-case detail (e.g. whether category is exact-match or prefix) beyond what the schema already supplies.

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 resource and scope: the latest Legacy COT report across every market, enumerating the returned fields (net positions of large speculators and commercials, week-on-week change, open interest). It is clear on its own, but it never distinguishes itself from the very similar sibling get_latest_positions, leaving an agent to guess which 'latest' endpoint to pick.

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?

Gives operational guidance — use offset to page through 100 markets per answer, filter by category — and notes availability at every account level. It does not say when to prefer this over get_latest_positions, get_history, or scan_extremes, so the usage decision against alternatives is left implicit.

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