OFAC sanctions screening API / OFAC sanctions check. Returns NO_POTENTIAL_MATCH or potential matches. Not a legal clearance.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Person or entity name to screen. | |
| country | No | Optional country. | |
| entity_type | No | Optional individual or entity. | |
| date_of_birth | No | Optional date of birth. |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate read-only and non-destructive. Description adds that it returns a specific value (NO_POTENTIAL_MATCH or potential matches) and clarifies it is not a legal clearance, which provides transparency beyond annotations.
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?
Description is concise, contains only essential information: purpose, return type, and a caveat. No unnecessary words.
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?
Tool is simple; description covers purpose, return type, and a caveat. It is complete enough for understanding usage. No output schema is defined, but the return type is mentioned in the description.
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?
Input schema already provides descriptions for each parameter. Description does not add additional meaning or constraints for the parameters, so it adds no value beyond schema.
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?
Description clearly states it's an OFAC sanctions screening API/check, and specifies return value and that it's not legal clearance. Purpose is clear and distinguishing from siblings by focusing on OFAC.
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?
Description does not provide explicit guidance on when to use this tool versus alternatives like check_ai_act_applicability or validate_eu_vat. It only describes what it does, so usage guidelines are lacking.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct compliance or verification domain: AI Act applicability, general company compliance, OFAC sanctions, EU VAT, and legal entity verification. The descriptions clearly delineate their purposes, so an agent can confidently select the appropriate tool.
All tool names follow a consistent verb_noun pattern in snake_case (check_ai_act_applicability, company_compliance_preflight, screen_ofac, validate_eu_vat, verify_legal_entity). This predictable naming convention makes the tool surface easy to navigate.
With 5 tools, the server is well-scoped for a compliance gateway. Each tool covers a major compliance/verification need, and the count is within the ideal 3-15 range, ensuring the set is neither sparse nor bloated.
The tool set covers the primary compliance checks (AI Act, OFAC sanctions, VAT, LEI, and company preflight). Minor gaps exist—such as other sanctions lists (e.g., UN, EU) or additional regulatory checks—but for a focused gateway, the coverage is solid and enough for typical workflows.