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

Goes well beyond the readOnly/idempotent annotations by disclosing auth modes (X-Api-Key or x402), the HTTP 402 anonymous path, per-call cost ($0.008 USDC, free for linked Connect keys), a 15/min rate limit, ~300s caching, and an explicit 'this is billing, not a side effect' clarification. This is exactly the extra context 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?

Front-loaded and section-labeled (Purpose, Behavior, Auth, Cost, Rate limit, Returns, Guidelines), which helps scanning, but the purpose sentence is duplicated verbatim and the trailing Tags line restates already-listed keywords. Real redundancy dilutes an otherwise well-organized 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?

Covers behavior, auth, billing, rate limits and downstream workflow, and since an output schema exists it need not detail return values. Only gap is any concrete guidance on the business parameters (e.g., symbol format/timeframe options).

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 nominally 100%, so the baseline is 3, but those descriptions are tautological ('Parameter `symbol` (string). Required.') and the description adds no syntax, format, or validation meaning for symbol/timeframe beyond implying BloFin data. Marginal value over 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?

States a specific verb and resource — fetching market context (BloFin OHLCV candles, Central Command indicators, open interest, news) — and its 'all-in-one' framing implicitly distinguishes it from single-purpose siblings like cc.market_news and cc.open_interest. An agent can tell what it returns without opening the 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?

Provides downstream guidance ('Compute / parse / backtest only — no live orders', feed into cc.agent_strategy with force_paper=true), but never states when to prefer this tool over its narrower siblings. Usage is implied rather than contrasted.

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