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

With no annotations, the description carries the full burden and does substantial work: it discloses the return contents (matches, list, programs, similarity score), the always-present metadata (lists that answered, entries screened, per-list publish date), and the credit cost. It omits auth requirements, rate limits, and error behavior, so not 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 what the tool screens and against which lists, followed by return shape, retention guidance, caveat, and cost. Sentences are dense but each carries information; the 'keep data_as_of' sentence is somewhat operational advice but justified by the tool's audit purpose.

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?

With no output schema, the description must explain returns, and it does: matches with list, programs and similarity score, plus coverage metadata and list vintages. The data_as_of retention warning and the legal-caveat framing make it complete for correct downstream use.

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?

Single parameter with 100% schema description coverage, so the schema already documents the 'name' field and its example. The description adds only the notion that aliases are included in matching, which is marginal parameter-level value; baseline 3 is appropriate.

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 (screens) and resource (person or company name) plus exact scope: OFAC SDN, OFAC Consolidated, UN Consolidated, aliases included. This is clearly distinguishable from the sibling verification/enrichment tools without opening any schema.

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 clear context for when this applies (sanctions screening of a name) and important interpretive guidance that a match is a due-diligence signal, not a legal determination, plus a cost note. It does not name alternatives or state when NOT to use it, so it falls short of 5.

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