market_stream_sample

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

With no annotations, the description carries the full burden but only mentions collecting events for a short duration. It does not disclose authentication requirements, connection lifecycles, or whether the operation is read-only, leaving significant behavioral gaps.

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 a single, front-loaded sentence with no unnecessary words. It efficiently communicates the core action.

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 complexity of a streaming tool with three parameters and no output schema, the description is insufficient. It omits details on return values, stream behavior (real-time vs. historical), and usage limits, leaving the agent underinformed.

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 provides partial meaning for 'dex' (DEX websocket stream), but offers no explanation for 'durationMs' or 'maxEvents', which are critical for controlling the streaming behavior.

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 opens a DEX websocket stream and collects events, with a specific verb and resource. It distinguishes from sibling tools like wallet_stream_sample by focusing on DEX 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 usage for short-duration data collection but provides no explicit guidance on when to use this tool versus alternatives (e.g., market_get_snapshot) or 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.