ws_subscribe_wallet

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

No annotations are provided, so the description must disclose behavioral aspects. It only says 'Subscribe' but does not explain the subscription lifecycle (persistent vs one-time), how updates are delivered, whether a subscription ID is returned, or if any connection setup is required. This leaves critical behaviors undisclosed.

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 fluff or redundant phrasing. It is concise and immediately clear, earning a high score for efficiency, though it could have included a bit more context without becoming verbose.

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 subscription tool within a family of ws_* tools, this description is incomplete. It does not mention how to receive updates (ws_get_updates), manage subscriptions (ws_list_subscriptions), or unsubscribe (ws_unsubscribe). Without an output schema, the absence of these lifecycle details leaves the agent without critical operational context.

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 input schema fully describes both parameters (address and chain) with clear descriptions. The description adds no extra semantic detail beyond the schema, so the baseline score of 3 applies given the 100% schema coverage.

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 states a specific verb ('Subscribe') and resource ('transaction notifications for a wallet address'), which clearly distinguishes it from sibling subscription tools like ws_subscribe_price or ws_subscribe_blocks. It precisely conveys what the tool does.

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 gives no guidance on when to use this tool versus alternatives. It does not mention that it is for wallet transaction alerts specifically, nor does it reference the need for ws_get_updates to retrieve notifications or ws_unsubscribe to cancel. No explicit exclusions or alternative tools are named.

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