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

With no annotations, the description carries the full burden and does a good job: it discloses the PASS/BLOCK output shape, the fail-safe behavior when lists are unavailable, keyless access, Ed25519 attestation, and the x402 paid endpoint with price. It does not cover rate limits or what happens on ambiguous matches, but the operational profile is substantially clearer than most tools here.

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 purpose is front-loaded in the first clause, and the following sentences are dense but each carries distinct information (verdict, fail-safe, payment, endpoint). The bracketed x402 metadata is somewhat cluttered, but nothing is redundant 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?

There is no output schema, and the description does step in with PASS/BLOCK, which is adequate. However it never clarifies the relationship between the three input parameters or which sibling tools to prefer, leaving real gaps for an agent choosing among many sanctions-adjacent tools.

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 only 33%: 'name' is documented while 'entity' and 'company' carry no descriptions. The phrase 'company or entity name' in the description usefully signals that these three parameters are near-aliases for the same input, which partly compensates. It still does not tell the agent which one to prefer or whether they are truly interchangeable.

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 states a specific verb and resource: 'Screen a company or entity name against multi-list sanctions (OFAC/EU/UN public designations index).' That is concrete enough for an agent to know exactly what the tool does. It does not, however, differentiate itself from close siblings such as lion_sanctions_screen or lion_multi_sanctions_bundle, which matters given the crowded sanctions family.

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?

There is no explicit when-to-use guidance and no mention of alternatives. The description says the tool is 'fail-safe if lists unavailable' but never states which screening scenario this tool is for versus lion_sanctions_screen, lion_multi_sanctions_bundle, or lion_wallet_screen. The agent is left to infer routing solely from the name.

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