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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so safety is covered. The description adds a genuinely non-obvious behavioral detail — that trust lines are 'capped' — which warns the agent about truncated results. It stops short of saying how many or whether other fields are also truncated, so it is strong but not exhaustive.

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 labeled segments — content, when to use, boundary/example — with zero filler. The most decision-relevant information (what it returns, when to call it) is front-loaded.

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?

An output schema exists, so return-value structure need not be explained, and the description still previews the fields. For a single-parameter read tool with full annotation coverage, nothing needed to call it correctly is missing.

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 100%, so the address format ('r..., checksum verified') is already documented. The description goes beyond the schema by supplying a concrete, correctly-formatted example call, which is useful for an agent constructing the invocation. It adds no further constraints, so it lands above the 3 baseline rather than at 5.

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 first sentence names the concrete resource (an XRPL account) and enumerates exactly what the summary contains — balance, sequence, owner count, transfer rate, trust lines. Combined with the title and the explicit scope note, an agent can distinguish it from get_network_health, get_amm, or get_orderbook without opening a 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?

It gives an explicit positive trigger ('inspect an account before building a transaction for it') and an explicit negative boundary ('Not for transaction history, reserves or account flags'). Both when-to-use and when-not-to-use are stated rather than inferred.

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