advanced_candle_pattern

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

With no annotations, the description carries full burden but only states a generic 'analysis' behavior. It does not disclose whether the tool is read-only, requires authentication, or has side effects like data mutation or rate limits.

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 description is concise with a clear one-line purpose followed by a parameter list. No extraneous information, though the structure could be improved with section headers.

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?

Without output schema or annotations, the description omits critical context such as return format, error handling, data source specifics, and how results relate to other tools. This is insufficient for a 5-parameter analysis tool.

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 Args section adds basic meaning to each parameter (e.g., exchange examples, timeframe options, ranges), but lacks precision (e.g., 'min_size_increase' as percentage of what? No enum lists for allowed values). Given 0% schema coverage, the description partially compensates but could be more detailed.

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 it performs 'Advanced candle pattern analysis using multi-timeframe data', which is a specific verb+resource combination. However, it does not explicitly differentiate from sibling tools like 'consecutive_candles_scan' or 'multi_timeframe_analysis', leaving some ambiguity.

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 provides no guidance on when to use this tool versus alternatives, nor any context about prerequisites or expected scenarios. It only lists parameters without explaining usage context.

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