scan_patterns_bulk

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It does not mention whether the operation is read-only, any rate limits, data freshness, or other behavioral traits beyond the action of scanning.

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 extremely concise—two sentences and an example. Every word adds value, no redundancy or filler content.

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?

While the description covers the basic scanning functionality and an output schema exists, it omits details like supported pattern names, prerequisites (e.g., valid exchanges), and return format characteristics. It is adequate but not fully complete given 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?

Schema description coverage is 0%, so the description must add meaning. It explains the symbols array and pattern_filter parameter, with an example showing usage. This provides context that the schema lacks, though it could detail symbol format more.

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 scans multiple stocks for candlestick patterns, with a specific verb ('scan') and resource. The example reinforces this purpose and implicitly distinguishes it from sibling detect_candlestick_patterns which likely handles single stocks.

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 mentions optional filtering by pattern name but does not provide explicit guidance on when to use this tool vs alternatives like detect_candlestick_patterns. No advice on when not to use it is given.

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