analyze_mtf_fibonacci

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

No annotations are provided, so description carries full burden. It mentions parallel computation and confluence detection but lacks details on side effects, output format, or potential performance implications.

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?

Single focused paragraph with a clear title prefix, no redundant words, and all information front-loaded.

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?

Given the complexity of multi-timeframe analysis and absence of output schema or annotations, the description fails to explain what the tool returns or how to interpret confluence zones, leaving significant 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 has 0% description coverage, but parameter names and defaults (pair, lookbackDays with sample values) provide basic meaning. No additional explanation of array usage or constraints beyond what schema enforces.

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 clearly states it performs multi-timeframe Fibonacci analysis with confluence zone detection, and explicitly distinguishes from sibling analyze_fibonacci by saying 'No need to call analyze_fibonacci individually.'

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 clear context for when to use this tool over analyze_fibonacci (for batch analysis across multiple lookback periods), but does not mention when not to use it or specify alternative tools.

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