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

With no annotations, the description carries the full load and does well: it discloses the return payload fields (score, programs, countries, aliases, OFAC link), freshness metadata (list as-of date, data age), a legal disclaimer ('not a legal determination'), and the pricing/payment mechanism. It omits auth/rate-limit details, keeping it just short of a 5.

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 trigger and input/output shape in tight, information-dense form; the example and price are useful for x402 callers. The single block is slightly crammed, but every sentence contributes.

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?

Substitutes for a missing output schema by naming the return fields and adding freshness and legal caveats, which is exactly what an agent needs before acting on a hit. The main hole is the undisclosed multi-list capability, which affects how results should be interpreted.

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 100%, so the schema already documents all five parameters, making 3 the baseline. The description corroborates fuzzy matching with aliases and gives a worked example, but it mentions only the OFAC list and never surfaces the `lists` parameter (eu, uk, all) that the schema exposes, so it undersells an agent-relevant capability.

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 (check/screen) and resource (name against the U.S. Treasury OFAC SDN list), covering persons, companies, vessels and aircraft. The 'OFAC sanctions name search' framing makes it clearly distinct from sibling sanctions_address, which screens addresses rather than names.

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?

Gives an explicit when-to-use trigger: 'before paying, onboarding or shipping'. This is clear operational context. It does not explicitly route between sanctions_screen and sanctions_address, though the name-vs-address subject matter makes the split fairly self-evident.

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