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

With no annotations, the description carries the burden and does disclose cost ($0.05), the 100-name batch ceiling, the three list sources, and that results are per-name best matches with list version, date and freshness. It omits matching semantics (fuzzy vs exact), how ties are resolved, and any failure/partial-result behavior when a name gets no hit.

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?

A single front-loaded sentence with the cost marker leading and no filler; every clause carries information. Density comes at a cost — abbreviations like 'FSF' and 'date and freshness' are terse to the point of ambiguity.

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 4-param paid batch tool with no output schema, the description gives a partial return picture ('per-name best match with list version, date and freshness') but leaves threshold semantics, 'lists' value format, and any output shape undefined. An agent can call it, but not tune or interpret it confidently.

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 coverage is only 25% — only access_token is documented. The description implicitly covers 'names' and 'lists' (naming the three regimes), but 'threshold' is a semantically load-bearing matching cutoff left completely unexplained, and no valid values are given for 'lists' (e.g. whether omitting it means all three).

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 and resource ('Screen up to 100 names') plus the covered regimes (UK, EU FSF, UN) and the batch cap, which is far more than a restatement of the name. It does not, however, distinguish itself from the sibling 'batch_screen' or 'sanctions_check', so an agent cannot tell from the text which of these overlapping tools to pick.

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 'up to 100 names in one call' phrasing weakly implies bulk use, but there is no explicit when-to-use, when-not-to-use, or routing to 'batch_screen'/'sanctions_check'/'counterparty_check'. The '$0.05' PRO marker hints at a cost tradeoff without stating the alternative.

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