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

The annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=false, and destructiveHint=false. The description adds meaningful behavioral context beyond these: parallel scoring, results ranked by score descending, a rank field, a required $0.10 fee, and a return structure. It also signals the fee prerequisite via get_fees(), which is valuable execution context.

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 front-loaded with the core purpose and includes a useful Returns line. The use-case bullets are helpful but somewhat promotional, and the phrase 'open reputation layer for XRPL agents' adds little actionable information. Still, the overall structure is efficient and scannable.

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 paid batch tool, the description covers all critical context: fee and fee_hash acquisition via get_fees(), parallel execution, ranking, result shape, and maximum batch size. The annotations handle safety profile, and the output schema covers return values. Nothing essential for calling this tool 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?

The schema covers both parameters with 100% description coverage. The description echoes the maximum of 50 and the fee amount, but doesn't add new semantic meaning beyond what the schema already provides. The baseline of 3 applies here because the schema carries the load.

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 uses a specific verb ('Score') with a specific resource ('XRPL wallets') and clearly scopes the operation to batches of up to 50. It also names the ranking behavior, which distinguishes it from the singular get_wallet_trust_score sibling. The purpose is unmistakable.

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 lists clear use cases (rank candidates, screen shortlists, build directories, due diligence) and implies the batch context through 'up to 50 in a single call'. However, it does not explicitly contrast this with the single-wallet sibling tool or state when to prefer one over the other, so it stops short of full guidance.

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