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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds a genuinely non-obvious behavioral trait beyond that: trust lines are returned 'capped', warning the agent that the result set may be truncated. It stops short of saying what the cap is or whether further pagination exists.

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-loaded with the return payload, then usage, exclusions and an example — a sensible ordering with no filler sentences. The field list is dense but every item is informative; the labeled structure ('When to use:', 'Prefer another tool:') is slightly formulaic but earns its space.

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 single-parameter read tool with an output schema, the description need not explain return values. Combined with annotations covering the safety profile and the description covering scope, the 'capped trust lines' caveat, and exclusions, an agent has everything needed to select and invoke it correctly.

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?

Only one parameter and schema description coverage is 100%, so the schema already documents the address format including checksum verification. The description's example call reinforces the shape but adds no semantic meaning (no hint about encoded addresses, tags, or malformed-input behavior) beyond what the schema states. Baseline 3 applies.

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?

Names the exact resource (an XRPL account) and enumerates the returned fields (XRP balance, sequence, owner count, transfer rate, trust lines), which is far more specific than the title 'Account summary'. The sibling landscape includes xrpl_account_lines and xrpl_account_transactions, and the description explicitly excludes both, so an agent can disambiguate 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?

Provides an explicit when-to-use ('inspect an account before building a transaction for it') and an explicit when-not ('Not for transaction history, reserves or account flags'), naming the sibling domains it overlaps with. The pre-transaction framing also implies the correct ordering relative to xrpl_payment_readiness.

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