smart_volume_scanner

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

No annotations provided, so description must cover behavior. It describes input parameters but does not disclose that the tool is read-only, non-destructive, or any potential rate limits. The output schema exists but is not detailed in the description.

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 brief and front-loaded with the purpose. The Args list is concise and includes defaults. Every sentence is necessary and well-formatted.

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 (5 parameters, output schema exists), the description adequately covers input param semantics. It does not explain the exact combination logic (e.g., AND/OR conditions) but defaults are clear from schema. Slightly incomplete on return value usage, but output schema handles that.

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 description adds significant meaning beyond the input schema titles. It explains 'min_volume_ratio' as minimum volume multiplier, 'min_price_change' as percentage, and defines 'rsi_range' values (oversold, overbought, neutral). This fully compensates for the 0% schema description coverage.

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 is a 'Smart volume + technical analysis combination scanner,' using specific verbs and resources. It distinguishes itself from sibling tools like volume_breakout_scanner and bollinger_scan by combining volume and technical analysis.

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 does not explicitly state when to use this tool over alternatives. It implies use for combined volume and technical scanning but lacks clear context or exclusion criteria.

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