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

No annotations are provided, so the description carries the burden for behavioral disclosure. It adds useful context by noting the tool is free and requires no auth, but it omits crucial behaviors like output format, what constitutes a match, or any rate limitations. This is minimal but not completely bare.

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 a single, tightly worded sentence that immediately communicates the core function and key differentiators (free, no auth). There is no filler or redundancy; every word contributes value.

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?

The tool is simple in terms of parameters, but it lacks an output schema and detailed behavior. The description does not clarify what the tool returns (e.g., boolean match, list of sanctions, or whether a clean result is also indicated). Given the sensitivity of OFAC screening, users likely need more context about the response semantics, so the description falls short of completeness.

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 input schema fully describes the single parameter ('EVM address to screen'), giving 100% coverage. The description does not add extra meaning beyond that, but since schema coverage is high, a baseline of 3 is appropriate.

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 verb ('screening') and resource ('address'), clearly identifying the tool's function: OFAC SDN counterparty screening. It is distinct from any sibling tool, making its purpose unambiguous.

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 implies usage by mentioning it is free and requires no auth, which suggests when it might be preferred (e.g., no authentication overhead). However, it does not explicitly state when to use this tool versus alternatives, nor does it describe exclusions or prerequisites beyond the address parameter.

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