stream_ohlc_snapshot

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

Without annotations, the description conveys that the tool seeds from REST and updates from stream data, but lacks details on side effects (e.g., whether it writes or only reads), lifecycle, or error handling. It does indicate data sources, but not the full behavioral contract.

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 two concise sentences that clearly state the workflow and when to use REST instead. It is front-loaded with the primary action and includes necessary context without extraneous detail.

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?

For a tool that combines REST and streaming, the description explains the seed-then-update flow and the completed-candle alternative, but lacks details on output format, subscription lifecycle, or error handling. Since no output schema or annotations are provided, the description covers the essential usage but leaves some implementation specifics undocumented.

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 gives context that the stream data is 5-minute and that REST is used for completed candles, which infers some parameter meaning (like timeframe), but it does not explicitly explain 'epic' or other parameter nuances beyond what the schema likely states. It adds moderate value.

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's function: to seed an in-progress OHLC candle from REST data and then update it from 5-minute chart stream data. It distinguishes itself from sibling tools like stream_updates and historical REST price tools by specifying the combined approach.

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?

Explicit guidance is given: use REST for historical (completed) candles and seed/update from stream for in-progress candles. The description clearly delineates when to use this tool vs. alternatives.

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