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

With no annotations, the description carries the full burden. It discloses the data source (append-only exposure snapshots), the visibility limitation (loans before first observation are invisible), the behavior for deleted loans (shown as vanished with everDefaulted true), and the observationWindow concept. It also mentions 'Free, no signup' as a practical access trait. This is thorough and transparent.

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?

The description is long but each sentence contributes meaning. It front-loads the core purpose, then explains per-loan details, an example, the observationWindow, and the parameter. It is structured logically and avoids fluff, though it could be slightly more compact without losing important nuance.

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 tool with no output schema, the description explains the output fields, the observationWindow, and the edge case of deleted loans. It gives the agent enough to know what to expect and how to interpret results. Missing error cases are minor and not critical for correct invocation.

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?

The schema already describes the borrower parameter as an XRPL classic address (r...), and the description repeats this without adding new meaning. It does not elaborate on formatting, validation, or any edge cases. Since schema coverage is 100%, the description adds minimal value beyond restating the parameter.

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 description states exactly what the tool does: returns the complete observed loan history for a borrower, including deleted loans, with specific fields like first/last ledger, status, and flags. It is distinct from other lending tools by emphasizing the historical, append-only nature and the 'credit file' concept. The verb 'get' plus the resource 'lending history' is clear and unambiguous.

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 clear context that this is for historical loan data, especially for loans deleted from the ledger, which is a unique use case. It implies when to use it (when you need the full credit file) but does not explicitly name alternatives like get_lending_exposure or state when not to use it. The context is strong, but no explicit exclusions or alternative routing is given.

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