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

With no annotations the description carries the full burden, and it discloses meaningful traits: cost ($0.005), payment mechanism (x402 paid GET on Base), and that results are Ed25519-attested. It omits auth requirements for the paid call and what a match vs no-match response looks like.

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 question, followed by a compact comparison, provenance, and endpoint metadata. The parenthetical is dense but every clause earns its place and nothing is padding.

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?

No output schema exists, so return shape rests partly on the description; 'fuller fields + multi-list metadata' hints at the response and the pricing/attestation round it out. It is adequate for a one-parameter screen, though a bit more on match output would help.

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 single 'address' parameter is fully described in the schema (100% coverage: 'EVM address to OFAC SDN / sanctions screen'). The description says 'this address' but adds no format, chain, or validation 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?

The opening question 'Is this address on the OFAC SDN list?' states a specific verb and resource, and the parenthetical 'same list as $0.001 wallet-screen, fuller fields + multi-list metadata' explicitly distinguishes it from the lion_wallet_screen sibling. Address-scope also separates it from lion_entity_sanctions_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?

It names an alternative (the $0.001 wallet-screen over the same list) and gives the condition that selects this one: fuller fields plus multi-list metadata. It stops short of a full when-not set, e.g. it does not contrast with lion_multi_sanctions_bundle or lion_entity_sanctions_screen.

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