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

There are no annotations, so the description carries the full transparency burden. It discloses that this is a read-only, public-ledger operation ('100% public ledger data'), that no API key or signup is required, and exactly what the caller receives. It stops short of covering failure modes or data freshness, but the essential behavioral profile is clear.

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 tightly organized: action and use case first, then the return payload, then the parameter, then access requirements. Every sentence adds useful information without fluff or repetition beyond a compact params reminder.

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 one-parameter tool with no output schema, this description is unusually complete. It explains what the score means, the range, the signals used, the returned artifacts, the required address format, and the access model, so an agent has enough context to 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?

Schema coverage is 100% for the single required parameter, and the schema already specifies that wallet_address starts with 'r' and is 25–35 characters. The description repeats these constraints rather than adding new semantic detail, so it meets the baseline but does not elevate it.

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 opens with a specific verb and resource: 'Get a 300–850 creditworthiness score for any XRP Ledger wallet.' It also enumerates the exact output components (score, letter grade, percentile, per-signal breakdown, tips), which makes the tool's function unmistakable and separates it from sibling tools like check_mpt_risk or issue_score_credential.

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?

The description gives clear usage context: 'before you pay, lend to, trade with, or onboard it.' It does not explicitly state when to avoid this tool or name an alternative for different wallet checks, but the intended decision-making context is well conveyed.

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