ofac_consolidated_list

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

The description does not disclose behavioral traits beyond the readOnlyHint annotation. It fails to mention pagination, default limit, filtering limitations, or update frequency, which would help the agent understand what to expect when invoking the 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?

The description is a single, front-loaded sentence that conveys the core purpose without unnecessary words. It is concise and well-structured.

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 description adequately explains what data the tool returns, but it lacks details on response format, how the limit parameter behaves, and how it compares to ofac_sdn_list beyond 'non-SDN'. This leaves some contextual gaps for a complete understanding.

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 fully documents the 'limit' parameter with its description and default value, so the description adds no additional parameter meaning. This aligns with the baseline score of 3 for high schema coverage.

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 uses a specific verb 'Get' and clearly identifies the resource as the consolidated non-SDN sanctions list. By specifying 'non-SDN' and providing examples (sectoral sanctions, foreign sanctions evaders), it distinguishes this tool from siblings like ofac_sdn_list.

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 conveys clear context about the tool's content, implicitly differentiating it from alternatives by highlighting 'non-SDN'. However, it does not explicitly name alternative tools or state when not to use this tool, leaving some guidance implied.

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