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

Annotations already declare readOnlyHint, destructiveHint=false and idempotentHint, so the 'Read-only' clause is largely redundant. However, the description adds real behavioral context beyond the structured fields: the specific detection heuristic (unexpected regular key / multisig signer list) and the urgency rule that changes in the last 7 days are flagged urgent.

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?

One dense sentence with zero filler: it leads with the core check, names the concrete threat pattern, and ends with the urgency rule and read-only status. Nothing could be removed without losing information.

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 an output schema present, return values need not be explained, and the description covers what is inspected and how findings are prioritized. It stops short of stating anything about failure modes (e.g., invalid address, network errors) or result interpretation, which would round it out.

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?

There is a single address parameter with 100% schema description coverage, so the schema already documents format and constraints. The description adds no extra parameter meaning, which is the correct baseline when the schema does the work.

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 and resource (checks whether anyone besides the owner can sign for an XRPL wallet) and enumerates the exact signals it inspects: unexpected regular key or multisig signer list. The wallet-focused scope cleanly separates it from the token-oriented siblings check_token_safety and is_it_the_real_token.

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 makes the use case implied (detecting takeover/drainer setups) but never says when to call this versus the sibling token-checking tools, nor any prerequisites or exclusions. Usage is inferable but not stated.

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