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

With no annotations, the description carries the full burden, and it does disclose one genuinely valuable behavioral trait: results are screening leads requiring adjudication, not definitive matches. It says nothing about whether this calls an external service, latency, rate limits, or what the response contains.

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 short sentences, purpose front-loaded, with the important cautionary caveat second. No filler and no redundancy with the schema.

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 simple two-parameter tool this covers the essentials of what it does and how to treat matches, but with no output schema there is no description of what a screening response looks like (candidate list, scores, alias hits). Combined with the fully undocumented min_score, an agent cannot call this tool 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 description coverage is 0%, so the description must explain both parameters and explains neither. The 'name' parameter is at least implied by 'screen a name', but 'min_score' (0.5-1.0 fuzzy threshold) — the parameter most likely to be misused — is completely undocumented anywhere.

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 (a name against the OFAC SDN list and aliases), which is far more informative than the bare tool name. It does not, however, distinguish itself from the similar-sounding sibling 'entity_lookup', so an agent must still guess which 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 only guidance offered is interpretive ('a match is a lead for review, not a determination'), which tells the agent how to read output but not when to invoke this tool versus entity_lookup or the other siblings. No prerequisites, no exclusions, no alternative routing.

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