scan_watchlist_for_intraday_opportunities

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

Without annotations, the description adds value by disclosing that the tool is slow and fetches multiple timeframes. However, it does not mention whether the tool is read-only, what it returns, or any permissions needed, leaving gaps.

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 with two sentences. The first sentence states purpose and output, the second adds a critical behavioral note. No fluff, 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?

The description covers the core purpose and a performance caveat, but lacks details on output format (e.g., list of symbols with scores), how confidence is calculated, and any prerequisites like market hours.

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 does not mention the 'max_symbols' parameter or its effect. Since schema coverage is 0%, the description should compensate but fails to explain how to control the number of symbols scanned.

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 evaluates the watchlist for 'intraday setups' and ranks them by confidence score. It distinguishes from the sibling 'scan_watchlist_for_swing_opportunities' by specifying the intraday focus.

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 warns that the tool is slow and fetches three timeframes per symbol, implying it should be used sparingly. However, it does not explicitly state when to use this tool versus alternatives or provide when-not scenarios.

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