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

With no annotations, the description carries the full disclosure burden. It does add real behavioral context — per-call cost of $1.00 USDC, the 50-name cap, and the important caveat that this is a 'screening aid only' rather than an authoritative determination — but it says nothing about what the response contains (match scores, confidence, list attribution), failure behavior for oversized batches, or authentication/payment mechanics.

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 sentences: capability and limit first, disclaimer second, usage example and pricing third. Every element earns its place for an agent weighing cost and format before calling, and nothing is padded.

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 paid screening tool with no output schema and no annotations, the biggest remaining gap is return-value shape — the agent cannot tell whether results are per-name verdicts, scores, or list-by-list flags. Cost, batch limit, and the screening-aid caveat are covered, so it is adequate but not complete.

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 0% and the schema itself is an untyped empty object, so the description is the only specification available. It supplies a concrete example showing a string array of names and states the 50-entry limit, which meaningfully compensates for the empty schema, though it never explicitly says the values must be strings.

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?

The description names a specific action (screen names against sanctions lists), the resource (OFAC/UK/UN/EU public lists), and the batch scope (up to 50 names in one call), which is enough to separate it from the single-name variant. The only weakness is that the sibling is referred to by endpoint path ('/sanctions') rather than tool name, so the pairing takes a moment to resolve.

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?

It gives a clear use condition (screening many names in one call) and explicitly routes the agent to alternatives: single-name screening via /sanctions at $0.05 and the onboarding pack via /kyb at $2.50. It lacks an explicit 'don't use this for' exclusion such as single-name lookups or non-name identifiers, which keeps it off a 5.

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