Live Bar Search (deprecated → use search(mode='live_bars'))

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

Annotations already provide behavioral hints (readOnlyHint=true, etc.), and the description adds only deprecation context. It does not contradict annotations. The description adds minimal additional behavior information beyond the structured 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?

The description is a single, front-loaded sentence that effectively communicates the deprecation and alternative. No wasted words; it is appropriately concise for this purpose.

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 tool is deprecated and has an output schema, the description minimally conveys the tool's purpose. However, it lacks guidance on parameter usage and expected behavior beyond the alternative. Acceptable for a deprecated tool but incomplete for full usage.

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%, and the description does not explain any parameters (bars, scale, top_k, cross_timeframe). Only 'bars' is mentioned in the alternative call. The description fails to compensate for the lack of schema descriptions.

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 is for 'Live Bar Search' and explicitly provides the alternative 'use search(mode="live_bars")'. This distinguishes it from sibling tools like 'search' and indicates its function despite deprecation.

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 explicitly states the tool is deprecated and directs users to use 'search(mode="live_bars")' instead, providing clear guidance on when not to use this tool and what alternative to use.

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