Collect a live window

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

Description discloses that subscriptions created are removed after the call, which is key behavioral context beyond annotations. It also specifies stop conditions (duration_ms or max). No contradictions with annotations.

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?

Two sentences, front-loaded with core action (subscribe, collect, cleanup) and a clear use case. Every sentence adds value with no redundancy.

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?

Covers essential behavior (cleanup, stop conditions) and intended use. Lacks explicit mention of return format, but implied by 'collecting matching ticks'. Generally complete for a simple tool.

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 baseline 3. Description adds value by explaining the product enum, providing symbols example, and stating defaults/bounds for duration_ms and max, which goes 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?

Description clearly states it subscribes, collects ticks for a duration or max, then returns them and removes subscriptions. It distinguishes from sibling tools like ws_subscribe (persistent) and ws_poll (polling existing).

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?

Explicitly says 'Use this for a quick sample N seconds of live data request', indicating when to use. Could be more explicit about when not to use or alternatives, but the sibling list provides context.

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