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

Annotations mark it read-only, and the description adds meaningful behavior: the list is refreshed daily, results are 'possible matches' with source list and match strength, and a match is not a legal determination. This gives an agent realistic expectations about output and limitations without contradicting the 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?

The description is three short sentences, with the core action front-loaded and each sentence earning its place: source list and freshness, output shape, and a legal-use caveat. There is no filler or redundant information.

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 one-parameter, read-only screening tool with no output schema, the description tells the agent what input to provide and what output to expect ('possible matches with their source list and match strength'). Nothing essential for correctly invoking the tool is missing.

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?

The only parameter, 'name', is fully described in the schema ('Company or person name to check'), and the tool description repeats that same concept. Since schema coverage is 100%, the baseline applies; the description adds no additional syntax, formatting, or edge-case guidance.

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 states a specific action ('Check ... name') against a specific resource ('U.S. Consolidated Screening List ... Commerce, State and Treasury: OFAC SDN, BIS Entity List and others'). This clearly distinguishes it from the sibling trade/export and license-verification tools.

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 description makes the use case obvious: screen a company or person name against U.S. restricted-party lists. It does not explicitly name alternatives or say when not to use it, but the context is unambiguous and none of the siblings overlap with this function.

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