cftc_cot_tff

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

The readOnlyHint annotation already declares safety, and the description adds a key behavioral constraint: the report covers financial futures only, which is beyond the annotation. It does not detail pagination or output format, but with annotation coverage and schema, the added scope information is valuable.

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, no wasted words. The tool's purpose, data scope, and use cases are front-loaded. Every phrase earns its place.

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?

For a simple read-only tool with 4 fully documented parameters and no output schema, the description covers purpose, scope, and usage examples. It does not explain return structure, but that is not required given the simplicity and annotation coverage.

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 baseline is 3. The description adds meaning by explaining the report categories (Dealer/Intermediary, etc.) and listing example market names (S&P 500, Treasury bonds, VIX) that map to the market_name parameter, going beyond the schema.

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?

The description starts with a specific verb+resource: 'Get Traders in Financial Futures (TFF) report data from CFTC.' It clearly distinguishes from sibling CFTC tools by stating 'Covers financial futures only' and listing the report categories, making the tool's scope unambiguous.

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 provides explicit usage context: 'Use for S&P 500, Treasury bonds, Eurodollars, VIX, currency futures.' It implies exclusion of non-financial futures via 'Covers financial futures only,' but does not explicitly name alternative tools for those cases.

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