smc_find_fair_value_gaps

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

Annotations (readOnlyHint, idempotentHint) cover safety, and description adds output structure and conceptual behavior (gaps rebalance). No contradictions, but the behavioral disclosure is adequate given annotations.

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?

Description is concise, with two short paragraphs and a returns line. Every sentence adds value, and the most important information is 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?

Tool is simple with a clear output shape described in the description. Annotations cover safety. Given the low complexity, the description is complete enough for an agent to use correctly.

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?

Input schema provides full descriptions for all five parameters, so the tool description does not need to repeat them. The description adds no parameter semantics beyond the schema, but schema coverage is high, meeting the baseline.

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 explicitly states it finds fair value gaps (three-candle imbalances) and reports zone, direction, and filled status. Differentiates from sibling tools like order blocks or liquidity sweeps by focusing on gaps.

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?

Description explains that unfilled gaps act as magnets and make natural entry or target zones, providing clear context for when to use the tool. However, it does not explicitly state when not to use it or compare to siblings beyond naming them.

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