xrpl_pulse_stream_purchase

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

Despite no annotations, the description discloses the paid nature, pricing tiers, that filtering is bound into the token (implying immutability after purchase), and the output format. It does not detail payment failure or refund policies, but covers the essential behavioral aspects.

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?

Two sentences convey cost, output, and core behavior with zero fluff. The pricing is front-loaded, and every clause adds information.

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?

Covers cost, output (JWT and ws_url), and the binding effect of filters, which is sufficient for a purchase tool. No output schema exists, so the explicit return description is valuable. It does not explain how to use the token, but that is likely covered by a separate streaming tool.

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 schema already describes all parameters, but the description adds meaning by explaining that source/signal/min_usd filters are 'bound into the token' at purchase and by associating duration tiers with concrete prices. This goes beyond the baseline 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?

Clearly states 'Buy a time-boxed WebSocket subscription to live Pulse events' with a specific verb and resource, distinguishing it from sibling query tools. Also mentions the return values (stream_token JWT and ws_url).

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?

Provides clear context that this is for paid live streaming with tiered pricing, implying use for real-time Pulse events. It does not explicitly state when-not-to-use or list alternatives, but the purpose is distinct from the many data-query siblings.

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