cap_stream_prices

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

No annotations provided; the description mentions WebSocket and duration limit, but omits connection lifecycle, error handling, rate limits, or what happens after duration ends. More behavioral disclosure is needed for a streaming tool.

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?

Single sentence is efficient and front-loaded with key action and constraints. Could be improved with structured parameter descriptions, but overall no wasted words.

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?

Despite having an output schema, the description lacks context on streaming behavior, connection management, and error scenarios. For a real-time tool, this is insufficient.

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 coverage is 0%, so description must compensate. It adds meaning for 'epics' (up to 40) and 'duration_s' (seconds), but does not explain 'update_interval_s'. This partial coverage is adequate but not complete.

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 verb 'stream', the resource 'live bid/offer for EPICs', and constraints like 'up to 40 EPICs' and 'for duration_s seconds', distinguishing it from sibling tools that stream candles or portfolio data.

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 real-time streaming use, but does not explicitly compare to alternatives like cap_market_prices (snapshot) or cap_stream_candles. It lacks explicit 'when to use' vs 'when not to use' guidance.

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