indicator_cci

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

No annotations are provided, so the description must disclose behavior. It only says 'Calculate', leaving unstated that the tool likely fetches OHLCV data for the symbol/timeframe and returns a series of CCI values; no side effects or error conditions are addressed.

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?

One sentence, no filler, front-loaded with 'Calculate the Commodity Channel Index (CCI).' The second half adds useful application context, so it 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?

With no output schema, the description doesn't state what the tool returns or how CCI values are delivered (e.g., array or single value). Given four parameters and a large sibling set, it also doesn't explain how inputs influence the result or when this indicator is preferred, leaving significant context gaps.

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 descriptions cover all 4 parameters (limit, period, symbol, timeframe), so baseline 3 applies. The description adds no parameter-specific meaning—it doesn't explain that period controls the lookback window or how limit/timeframe affect the calculation.

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?

Description opens with 'Calculate the Commodity Channel Index (CCI)', a specific verb and resource. It adds a short use case ('detects overbought/oversold conditions and trend reversals'), but doesn't contrast with sibling oscillators like RSI or stochastic, so it only partially differentiates.

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 implies usage for technical analysis when overbought/oversold or reversal signals are needed, via 'detects overbought/oversold conditions and trend reversals.' No explicit when-to-use, exclusions, or alternatives are given, which matters because many sibling indicators serve similar purposes.

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