consecutive_candles_scan

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

No annotations provided, so the description carries the full burden. It describes parameters but doesn't mention side effects, rate limits, or data freshness. For a read-only scan, this is adequate but could be improved.

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-line purpose followed by a clean bullet list of parameters. Every sentence adds value, no fluff. Front-loaded and efficient.

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?

No output schema, but the return behavior (list of matching coins) is implied. The description could specify ordering or result details, but for a simple scanner it is reasonably complete.

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 0%, but the description lists all 6 parameters with concise explanations (e.g., 'pattern_type: bullish (growing candles) or bearish (shrinking candles)'), adding meaning beyond the schema's titles and defaults.

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 clearly states 'Scan for coins with consecutive growing/shrinking candles pattern,' providing a specific verb (scan), resource (coins), and pattern type. This differentiates it from sibling tools like 'advanced_candle_pattern' or 'bollinger_scan'.

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 gives parameter details but does not provide guidance on when to use this tool vs. alternatives. With many sibling scanners, explicit context for selection is lacking.

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