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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description adds the cost model, the one-per-day rate limit, and that results come from a validated ledger (data-freshness context). It does not describe latency, pagination, or what happens when the daily quota is exhausted, but the rate/cost disclosure is the valuable part beyond 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?

Front-loads the cost/quota constraint, then the use case, then the return shape, then the paid alternative — a logical order with no filler sentences. The parenthetical failure list is dense but each item is load-bearing; slight compression loss is acceptable.

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?

No output schema exists, but the description states the return contents (verdict, blockers, cautions) and their source (validated ledger), plus the quota and the paid upgrade path. For a 7-param, single-required-param check tool this is enough for an agent to call it and interpret the result.

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?

With 57% schema description coverage across 7 params, the description compensates by tying failure modes to specific inputs: destination_tag (missing tag), destination (unfunded/deleted account), currency+issuer (no trust line, wrong issuer). It says nothing about source, network, or amount semantics, so the coverage gap is only partly closed.

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 ('check before sending XRP or a token on the XRP Ledger') and enumerates the failure classes it detects (missing destination tag, unfunded/deleted account, no trust line, wrong issuer). It also explicitly distinguishes itself from the sibling send_check, so an agent can route without opening either schema.

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?

Gives an explicit precondition ('Before sending XRP or a token'), a constraint ('Free, one per user per day'), and names the alternative with the condition that selects it ('The paid send_check adds the full evidence and has no daily limit'). When-to-use and when-to-escalate are both covered.

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