Batch Wallet Trust Scores

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real value beyond that by disclosing the $0.10 fee (XRP or RLUSD) and the parallel, ranked-descending output behavior. It does not explain why the operation is non-idempotent despite being read-only, which is the one notable behavioral gap.

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 core capability, batch limit and fee, then organized into scannable use-case bullets. The explicit 'Returns:' block is somewhat redundant since an output schema exists, which is the main wasted line.

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?

With annotations, a 100%-covered schema and an output schema present, the description supplies the fee prerequisite and ranking semantics an agent needs to call it correctly. Minor gaps remain: it doesn't say how partial failures or invalid addresses within the batch are handled.

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 100% and both parameters are fully documented in the schema, including the 50-address cap and the fee_hash payment details, so baseline 3 applies. The description's mentions of 'up to 50' and the $0.10 fee simply restate what the schema already says rather than adding new semantics.

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?

States a specific verb, resource and scope: 'Score up to 50 XRPL wallets in a single call', which immediately separates it from the single-wallet sibling get_wallet_trust_score. It also names the batch limit, parallel execution, and ranking behavior, so an agent knows exactly what the call produces.

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?

Four concrete use cases (rank candidates, screen bidders, build directories, pre-hire due diligence) give clear context for when this tool applies. However, it never states when NOT to use it, nor explicitly names the single-wallet alternative for one-off lookups.

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