cap_stream_candles

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

No annotations are provided, so the description carries the full burden. It adds key behavioral details: WebSocket-based, up to 40 EPICs, example resolutions and bar_type. However, it does not disclose error handling, rate limits, or reconnection behavior.

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?

Extremely concise: two sentences with no filler. Every word adds value, including the constraint on EPICs and the examples for resolutions and bar_type.

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 output schema exists, return values need not be explained. The description covers the core streaming functionality and key parameters, but lacks details on duration and update interval. Adequate for basic use, but not fully comprehensive.

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 compensate. It adds meaning for epics (up to 40), resolutions (example values), and bar_type (options). However, duration_s and update_interval_s are not explained, leaving gaps.

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 streams live OHLC bars for up to 40 EPICs at given resolutions, distinguishing it from sibling streaming tools like cap_stream_prices or cap_stream_alerts. The verb 'stream' and resource 'OHLC bars' are specific.

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?

No guidance on when to use this tool versus alternatives such as cap_stream_prices. The description only states what the tool does without any when-to-use or when-not-to-use context.

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