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

Beyond readOnlyHint/openWorldHint, the description discloses genuine behavioral traits: each payment is 'independently re-checked on the ledger', an 'explicit note' is emitted when the window is not fully covered, and it spells out billing edge cases ('Bad input and ledger outages are never charged') and the free-first-call-per-day rule. These are exactly the non-obvious traits an agent needs and cannot get from annotations.

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?

What the tool does is front-loaded in the first sentence, and the remaining sentences each carry distinct weight (coverage caveat, use case, pricing, error policy). It runs slightly long with pricing detail, but no sentence is pure filler.

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?

With no output schema, the description still conveys coverage behavior, cost model, and failure handling, which is substantial for a billing-sensitive tool. The main residual gap is the return shape (what a 'payment' record contains) and the role of the limit parameter, though both are minor given the free/simple listing nature.

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 only 33% (only min_value carries a description, and even that is just 'At least 50000'). The description compensates partially by tying the 120-minute maximum to 'up to 120 minutes' and the threshold to '50,000+ XRP', but it says nothing about what limit does or how to choose it, leaving one of three parameters undocumented in both places.

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?

States a specific verb and resource ('Lists large XRP Ledger payments') plus a concrete threshold (50,000+ XRP or major stablecoins) and window cap (up to 120 minutes), so the agent knows the scope precisely. It does not name or rule out any sibling (e.g., payment_check, payment_watch), so differentiation is left implicit.

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?

'Useful for market and liquidity monitoring' implies a use context but gives no when-not guidance and never points to an alternative sibling. The pricing rules ('first call each day ... free', 'A payment watch is paid from the first call') hint at cost trade-offs but do not explicitly route an agent between this tool, payment_check, or payment_watch.

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