zetrix_ws_subscribe_tx

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 subscribing to notifications but doesn't disclose behavioral traits such as whether this is a persistent subscription, how notifications are delivered, rate limits, authentication needs, or error handling. This leaves significant gaps for a tool that likely involves real-time updates.

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, direct sentence with no wasted words. It's front-loaded and efficiently conveys the core action, making it easy to parse quickly.

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 WebSocket subscription tool with no annotations and no output schema, the description is incomplete. It doesn't explain what happens after subscription (e.g., notification format, how to receive updates), potential side effects, or integration with other WebSocket tools, leaving the agent with insufficient context for effective use.

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 has 100% description coverage, with the 'addresses' parameter clearly documented. The description adds minimal value beyond this, as it only restates that addresses are involved without providing additional context like format examples or constraints. Baseline 3 is appropriate given the high 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 clearly states the verb ('subscribe') and resource ('transaction notifications for specific addresses'), making the purpose evident. However, it doesn't differentiate from sibling tools like 'zetrix_ws_connect' or 'zetrix_ws_submit_transaction', which are also WebSocket-related, so it lacks sibling distinction.

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?

No explicit guidance on when to use this tool versus alternatives is provided. It doesn't mention prerequisites (e.g., needing a WebSocket connection via 'zetrix_ws_connect'), exclusions, or comparisons to other subscription or transaction tools in the sibling list.

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