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

With no annotations, the description must carry the full behavioral burden. It adds useful constraints such as the 200-name batch cap, the 50–100 fuzzy threshold, and an audit-ready output with a list version, but it omits details like read-only safety, threshold defaults, and what happens when limits are exceeded.

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 two compact sentences and front-loads the key capabilities: batch size, threshold control, and output style. There is minimal waste, making it easy for an agent to parse quickly.

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?

Given the absence of annotations and an output schema, the description is only minimally adequate. It identifies the screening action and key limits but does not explain what lists are screened against, the precise output structure, or error behavior for oversized batches.

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?

Schema description coverage is only 33%, so the description must compensate. It provides meaningful semantics for the two core parameters: 'names' is capped at 200 per batch, and 'threshold' is an adjustable fuzzy threshold in the 50–100 range, while the access_token parameter is documented in the schema.

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 and resource: screen up to 200 names in a batch, with fuzzy matching controlled by a threshold. It is clear what the tool does, but it does not explicitly distinguish itself from siblings such as sanctions_check or regime_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 batch limit of 200 and the threshold range imply when the tool is appropriate, but the description does not explicitly say when to use it instead of sanctions_check or regime_list. Usage is implied rather than guided.

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