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

With no annotations provided, the description fully carries the burden. It transparently discloses the nature of the output (a receipt attesting to process, not ground truth), clarifies that a 'no match' is not a statement of being clean, and includes legal disclaimers. It also conveys the operation is non-destructive (compare and receive receipt) and free.

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 excessively verbose and repetitive. Key caveats are stated multiple times (e.g., 'not legal or compliance advice', 'NOT a statement that the address is clean'). It could be condensed into a few concise sentences without losing meaning, so it scores below average.

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?

Given the tool has no output schema, the description compensates by clearly enumerating return fields (queryId, list, result, statement). It also includes operational details like the terms of service and cost (free), making it complete for an agent to invoke 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?

The schema already provides full coverage of the single 'address' parameter, including type, format, and requirement. The description adds no substantive meaning beyond the schema, merely restating 'Params: address (r..., required)', so it meets the baseline of 3.

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 clearly states the tool's purpose: comparing one XRPL address against an OFAC SDN list snapshot and returning a receipt. It also specifies the exact scope (OFAC SDN only, no EU/UK/UN lists), which distinguishes it from potential sibling tools.

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 implicitly guides usage by specifying the scope (OFAC SDN only) and directs users to verify the receipt later with 'verify_attestation'. However, it does not explicitly name alternative tools for non-OFAC screenings, though the sibling list includes other tools.

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