xrpl_pulse_recent_events

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

With no annotations, the description must bear the transparency burden. It discloses the $0.10 cost, newest-first ordering, and the heterogeneous event types, which are important behavioral traits. It does not explain payment mechanics (how payment_signature is used), rate limits, or confirm read-only status, leaving some ambiguity for a paid HTTP-style 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?

Three short sentences, leading with the cost, then the core purpose, then content and filters. Every phrase earns its place, and the description is front-loaded with the most decision-relevant fact (the $0.10 charge). No fluff or repetition.

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 read-only-looking paid feed with 6 parameters and no output schema, the description covers the essentials: cost, content scope, ordering, and filters. However, it omits pagination behavior (despite before_iso implying backward pagination) and does not hint at response shape. This is adequate for a simple recent-events tool but not fully comprehensive.

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 coverage is high (83%), but the description adds meaning by mapping the 'kind' filter to the listed event categories (news, whale activity, lifecycle, Sentinel, RWA), clarifying the enum values. It also links 'min whale USD' to the filter and groups since_iso/before_iso as 'time range', which the schema already details. This adds value without redundancy.

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 this as a feed of recent XRPL signal events with a mixed content scope (news, whale activity, lifecycle, Sentinel, RWA). It lacks an explicit verb like 'list' but 'most-recent ... events' plus 'filterable' effectively conveys retrieval. It distinguishes from siblings by emphasizing the broad mixed feed and newest-first ordering, though it doesn't name a specific alternative.

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 obtaining a broad, mixed feed of recent XRPL events and highlights filterability by kind, time range, and whale USD. The upfront cost note is useful usage context. However, it offers no explicit when-to-use vs. sibling tools or exclusions, so agents must infer suitability from the content mix.

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