ofac_sdn_list

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

Annotations already declare readOnlyHint=true, so the read safety is covered. The description adds that it 'returns top entries' and is a 'large list,' providing useful behavioral context about output size, though it leaves 'top' undefined and does not explain ordering or default return count.

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?

Three short, front-loaded sentences with no filler. Each sentence adds distinct information: what it gets, what it returns, and how to control size. The description is efficient and easy to scan.

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 tool with no output schema, the description is adequate but leaves ambiguity about 'top entries' and lacks comparison to related OFAC tools. It does not clarify whether results are sorted, paginated, or what fields entries include, but the essence is captured.

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 schema covers the single 'limit' parameter with a clear description, and the description reinforces its purpose by saying the list is large and that limit controls size. This adds meaning beyond the basic schema by explaining why the parameter matters in practice.

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 clearly states the action ('Get') and resource ('OFAC SDN list'), and adds context that it is 'primary U.S. sanctions targets.' It does not explicitly contrast with sibling tools like ofac_search or ofac_consolidated_list, but the purpose is specific enough to distinguish the SDN list from other OFAC-related 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?

No when-to-use vs alternatives guidance is provided; there is no mention of ofac_search, ofac_filter, or ofac_consolidated_list. The only usage tip is 'Large list; use limit to control size,' which addresses the limit parameter, not tool selection.

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