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

No annotations are provided, so the description carries the full disclosure burden. It conveys that this is a read operation with optional payload expansion, but says nothing about defaults (which ledger is read when ledger_index is omitted), rate limits, or what the response contains.

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?

A single compact sentence that front-loads the core resource before the optional qualifiers. Efficient, though terse enough that it leaves gaps unaddressed.

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 three-parameter read tool with no annotations and no output schema, the description covers the what but omits how ledger_index resolves (default validated ledger?), what header fields are returned, and how expand interacts with transactions.

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 description coverage is 0% and there are three undocumented parameters. The description partially compensates by mapping 'transaction hashes' to the transactions flag and 'expanded transactions' to expand, but ledger_index is left entirely unexplained, including its default behavior.

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?

Specific verb 'Read' plus resource 'XRPL ledger header and metadata', with the optional payloads named. It does not, however, distinguish itself from the sibling n9t2_xrpl_ledger_data, which an agent would reasonably confuse with this tool.

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?

No when-to-use or when-not-to-use guidance is given, and no alternative is named despite a near-duplicate sibling (n9t2_xrpl_ledger_data). The only contextual hint is that transactions/expand are optional.

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