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

No annotations are provided, so the description carries the full burden. It discloses the decision semantics (which verdicts abort vs proceed), that the receipt contains an OFAC snapshot date and address count, and the pricing/cost ($0.01 Base USDC) and payment mechanism (x402 paid GET endpoint). It does not, however, describe what data source or freshness guarantee backs the OFAC snapshot beyond the date field, nor error/rate-limit behavior.

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 operative question, then the verdict mapping, then routing guidance, then pricing. Every clause carries information; no filler.

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 2-param, no-required-param read tool with no output schema, the description covers purpose, routing, verdict semantics, receipt contents, and cost. The main gap is that neither required params nor failure modes are addressed, but the definition is otherwise self-sufficient for correct invocation.

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% with both parameters fully documented (domain screened against entity-name lists, address checked against OFAC SDN snapshot). The description adds no syntax or format detail beyond the schema, so the baseline of 3 applies.

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 the decision the tool answers (should I pay this wallet), the mapping of verdict to action (STOP/HOLD abort, GO proceeds), and what the receipt contains. Distinguishes itself from lion_wallet_screen explicitly as a re-check rather than a first screen.

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?

Explicit when-to-use ('when paying this address again') and when-not-to-use with a named alternative ('Not the first screen — use lion_wallet_screen for that'). This is exactly the routing information an agent needs and rare to see this clearly stated.

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