xrp_subscribe

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

With no annotations, the description must disclose behavioral traits, but it only says 'real-time' without explaining that the subscription is persistent, how to unsubscribe, connection lifecycle, or what events look like. It also fails to mention any required authentication or rate limits.

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 with no fluff. It earns its place by stating the core purpose, though it could have been more informative with additional context.

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 tool's complexity (a live subscription mechanism) and the absence of an output schema or annotations, the description is incomplete. It does not explain what the response/stream contains, how to handle multiple streams, or the implications of subscribing (e.g., resource usage).

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% (streams and accounts are described), so the baseline is 3. The tool description adds no additional parameter meaning; it only restates the broad action.

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 identifies the action (subscribe) and the resource (real-time ledger updates), distinguishing it from the many data-retrieval tools among siblings. However, 'ledger updates' is narrower than the schema's mention of streams (ledger, transactions, etc.), so it's slightly imprecise.

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 phrase 'real-time' implies this tool is for live updates rather than one-time queries, which contrasts with the sibling get_* tools. But there is no explicit when-to-use guidance, no exclusions, and no mention of alternatives like polling.

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