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

With no annotations, the description carries the full burden. It usefully discloses that matching includes aliases, that results are the best 3 matches, and that each carries a score, but says nothing about what happens on no match, the match threshold, or any rate/auth constraints.

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?

Three short, front-loaded fragments with no filler; the cost signal leads and the scope and return shape follow. The telegraphic style ("Best 3 matches with score") is slightly clipped but nothing is wasted.

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 no annotations, so the description is the only source of behavior. It covers cost, scope, alias handling and the shape of the return, but omits no-match behavior, score interpretation, and which OFAC lists are covered.

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?

Only one parameter at 0% schema description coverage, so the description must compensate. It adds real value by saying the input is a person/company/vessel name and is single-valued, but gives no format expectations or examples for the `name` string.

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?

Specific verb ("Screen") plus a named resource (OFAC SDN list) and the entity types it accepts (person/company/vessel). The word "one" implicitly separates it from batch_screen, but no sibling is actually named.

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?

"FREE" and "screen one ... name" imply the use case (single-entity screening at no cost), but there is no explicit when-to-use, no exclusion, and neither sibling (batch_screen, program_list) is referenced as an alternative.

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