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

No annotations are provided, so the description carries the full burden. It usefully discloses that it is free and that it returns the best 3 matches with a score, but says nothing about match semantics (fuzzy vs exact), thresholds, rate limits, or auth requirements for a compliance-critical screen.

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?

Two compact sentences with zero waste. The cost signal ("FREE") is front-loaded and the return shape follows immediately.

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?

For a screening tool with no annotations and no output schema, the description covers purpose, cost, and return shape, but leaves the agent guessing on match semantics, score scale, and any request constraints before calling.

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?

With one parameter at 0% schema coverage, the description must compensate. It clarifies that the "name" input accepts a person or company name, which adds real meaning, but does not specify accepted formatting (e.g., full name vs first/last split).

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 ("Screen") and resource ("UK Sanctions List (FCDO/OFSI)"), with a clear scope of "one person or company name". The "one" scope and "UK" qualifier implicitly distinguish it from batch_screen and global_batch_screen, though no sibling is named explicitly.

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?

The single-name and UK-list scope implies when this tool applies vs batch and global siblings, and "FREE" signals no-cost screening. However, there is no explicit when-to-use / when-not-to-use statement or named alternative, leaving routing to inference.

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