smc_find_order_blocks

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

Description adds context beyond annotations by explaining the concept of order blocks, mitigation, and the output structure. Annotations already declare readOnlyHint, idempotentHint, etc., so the description enriches behavioral understanding without contradiction.

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, front-loading the core definition and purpose, then briefly explaining the concept and output format. It is not verbose but could be slightly more structured.

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 availability of an output schema (implied by context signals), the description sufficiently explains the tool's purpose and output. The annotations cover safety aspects, making the description adequate for the tool's complexity.

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 input schema includes descriptions for each parameter (symbol, interval, etc.), so the tool description does not need to repeat them. The description adds a partial output schema example but does not enhance parameter semantics beyond what the schema provides.

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 the tool finds order blocks, defines them as 'the last opposite candle before a structure break,' and lists the returned data fields. This distinguishes it from sibling tools which focus on fair value gaps, liquidity sweeps, etc.

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 implies the tool is for identifying order blocks in trading analysis and notes that unmitigated blocks are typically watched, but it does not provide explicit guidance on when to use this tool versus alternatives like smc_find_fair_value_gaps.

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