CME futures positioning (weekly COT report, BTC + ETH)

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds genuinely new context: data provenance (official CFTC), freshness ('updated every Friday'), and an interpretive caveat that hedge fund shorts are largely basis trade so week-over-week change matters more than level. That interpretive note is exactly the kind of behavioral insight annotations cannot carry.

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?

Three sentences, each earning its place: the trigger first, then the returned payload and cadence, then the interpretation caveat. No filler and the actionable when-to-call clause is front-loaded.

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 carries the burden of describing returns and does so (net positions, WoW changes, open interest, extremes/streaks) plus update cadence. For a zero-parameter read-only tool, an agent has everything needed to invoke and interpret it.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The schema is empty and fully consistent with the description.

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 names the specific data source (CFTC Commitments of Traders), the assets covered (Bitcoin/Ethereum) and the unit returned (net contracts), which is far beyond a restatement of the name. It does not, however, contrast itself with the sibling get_positioning, which an agent could easily confuse with this one.

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 gives explicit invocation triggers ('when the user asks how hedge funds or institutions are positioned', 'or about the CFTC Commitments of Traders report'), which is strong positive guidance. It stops short of stating when not to use it or which sibling to prefer for other positioning views.

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