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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only names the data source and use case, without mentioning any behavioral traits such as full-text search semantics, result set behavior, pagination, or potential limitations. The description adds little beyond what the schema already implies.

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 extremely concise, consisting of two short sentences. It front-loads the key identifier ('US Consolidated Screening List') and immediately states the intended use, with no wasteful or redundant text.

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 has 6 parameters and no output schema or annotations. The description provides a clear use case and data source, which is enough to differentiate it from siblings. However, it lacks any detail about what the search returns, how matches are scored, or whether special list filtering is required, leaving some contextual gaps for a tool used in due diligence.

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 has 100% parameter description coverage, so the baseline is 3. The description does not add any parameter-level meaning; it only provides a top-level context that the list is the US Consolidated Screening List. This context slightly enhances the meaning of 'list_name' but is not essential.

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 identifies the tool as operating on the US Consolidated Screening List, which is a restricted-entity search. The intended purpose (supplier/counterparty due diligence) is explicit. However, it doesn't use a direct verb like 'searches' or 'queries,' leaving the action slightly implied by the tool name.

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 specifies a clear use case: supplier/counterparty due diligence against export-control and sanctions lists. This differentiates it from sibling tools (e.g., trade flows, mineral deposits). It doesn't explicitly state when not to use it, but the context is sufficiently specific.

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