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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds substantial behavioral context beyond that: data lags several days, weekly release cadence, no real-time capability, and the requirement of a paid data vendor for real-time basis. These are exactly the behavioral traits an agent needs to know and they contradict nothing in 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?

The core value is front-loaded ('net long/short Leveraged Funds + Asset Managers, plus perubahan vs minggu lalu') before the critical caveat about data lag and non-intraday nature. Every clause earns its place and the caveat is essential. Slightly dense with parentheticals and informal register, but nothing is wasteful — a tight, informative block.

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 read-only report tool with a single enum parameter, the description covers the data provided, the two fund categories, week-over-week change, data lag timing, and scope limits (no real-time vs Binance). The annotations cover safety and the schema covers the parameter fully. The only gap is return-format details, but no output schema exists and the description compensates well otherwise.

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 the single coin parameter is already fully documented with its enum (BTC/ETH) and a description. The tool description's mention of Bitcoin/Ether aligns with the schema but adds no new parameter-specific meaning beyond what the schema provides. The baseline 3 is appropriate when the schema does the heavy lifting for a single well-documented parameter.

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 states a specific resource (CFTC Commitment of Traders weekly report for CME Bitcoin/Ether contracts) and what it delivers (net long/short for Leveraged Funds and Asset Managers, plus week-over-week change). It clearly differentiates this from the many Binance intraday tools in the sibling list by positioning it as a lagged weekly institutional-positioning report, so an agent can tell it apart without opening any 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?

The description explicitly says when NOT to use it: 'BUKAN sinyal intraday' (NOT an intraday signal) and 'gak ada real-time basis vs Binance' (no real-time basis vs Binance), giving clear exclusion context. It explains the data cadence (released Friday, positions as of Tuesday). It doesn't name a specific alternative tool to use instead, which keeps it from a 5, but the temporal caveats strongly steer appropriate use.

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