ws_subscribe_pool

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 discloses that this is a subscription (stateful) but does not explain how updates are delivered (e.g., via ws_get_updates), whether the subscription persists, or how to manage cancellations. This is a critical gap for a WebSocket subscription tool.

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, efficient sentence front-loaded with the action and resource. It contains no fluff.

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?

With no output schema and no annotations, the description should explain the subscription behavior, event retrieval, and lifecycle. It only provides a one-line overview, leaving the agent without essential context on how to use the subscription results or manage the subscription.

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 100%, so baseline is 3. The description adds a mapping of events to 'swaps, adds, removes,' which may be confusing since the schema uses 'swap', 'mint', 'burn', and 'sync'. It doesn't add meaningful parameter semantics 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 subscribes to DEX liquidity pool events, listing event types. It distinguishes from sibling subscription tools (ws_subscribe_price, ws_subscribe_wallet, ws_subscribe_blocks) by specifying the resource as DEX liquidity pool events.

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 monitoring pool events but provides no explicit guidance on when to use this over alternatives like ws_subscribe_wallet or ws_get_updates. It doesn't mention prerequisites or alternatives, though the event focus makes it somewhat clear.

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