stream_wallet_orders

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 mentions WebSocket, first event, and timeout, but does not explain behavior after timeout (no event? error?), whether it is a one-shot connection, or reconnection handling. Adequate but not thorough.

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 sentences, front-loaded with the core action, and contains no extraneous words. Every sentence serves a purpose.

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 tool uses WebSocket and has a timeout, the description does not explain what the return value looks like or what happens on timeout (e.g., error vs null). No output schema exists, so more detail would be helpful. Adequate but incomplete.

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 100%, so the baseline is 3. The description adds value by clarifying that walletAddress is required only if ALPHA_MNEMONIC is not set, and notes the default timeout. This provides context beyond the schema.

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 watches a wallet for order changes via WebSocket and returns the first change event. It distinguishes from sibling stream tools like stream_market or stream_orderbook by specifying the scope (wallet orders).

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 specifies the prerequisite: must provide walletAddress or set ALPHA_MNEMONIC. However, it does not explicitly state when to use this tool versus alternatives like stream_market or stream_orderbook, nor does it mention when not to use it.

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