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

No annotations exist, so the description carries the full behavioral burden. It names the data sources screened but says nothing about match semantics, fuzzy vs exact matching, whether absence of a hit means clean, rate limits, or whether country scoping changes results. That is a large gap for a compliance-screening tool.

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?

One front-loaded sentence with the alias relation stated first and no filler. It is appropriately sized, though brevity here reflects under-specification rather than economy.

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 annotations, no output schema, and undocumented parameters, the definition is not complete enough for an agent to call it confidently. It omits return shape (hit/no-hit, confidence), which matters more than usual because there is no output schema to fall back on.

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 description adds no meaning to the two properties. It does not explain the expected format of entity_name (legal name vs individual), nor what the optional country parameter does or whether omitting it broadens the search.

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 gives a specific verb and resource ('Screen a company or individual against OFAC SDN sanctions, HHS OIG exclusions, SAM federal debarment, and EPA ECHO enforcement'), which distinguishes it from the lookup/validate siblings. It also declares itself an alias for screen_sanctions_ofac_oig, so an agent knows the underlying capability.

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 identifies the screening use case implicitly but never says when to pick this alias over the sibling screen_sanctions_ofac_oig, nor what prerequisites or exclusions apply. The agent is left to infer that the two tools are interchangeable.

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