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

No annotations, so the description carries the full burden; it does add real value by disclosing the 200-name cap, the constraining threshold, and that output is audit-ready with list version and timestamp. It omits what a screening result contains (match/no-match semantics), default threshold behavior, and what happens past 200 names.

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 compact sentence that front-loads the PRO gate and the core capability, then the output guarantee. No filler, though the 'PRO.' prefix is cryptic without context.

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 and no annotations, the description should explain return shape and failure modes for a batch screening operation; it only hints at 'list version and timestamp'. What list is screened against and what a result record looks like remain unknown to the agent.

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 33% (only access_token documented), so the description must compensate: it explains names as up to 200 entries and threshold as adjustable, which helps. However, it gives no default, range, or meaning for threshold and doesn't clarify that access_token is the PRO-subscriber credential.

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+resource (screen names) plus a concrete scale limit (up to 200) and adjustable threshold, which contrasts with the singular-sounding sibling ofac_check. It never names the alternative for single checks, so sibling differentiation is implied rather than stated.

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 200 names at once' framing implies this is the bulk path versus the single-record sibling, but no explicit when-to-use/when-not or alternative routing is given. An agent must infer that ofac_check is the fallback for one-off lookups.

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