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

With no annotations, the description carries the full burden. It helpfully discloses that the screen is free, covers aliases, and returns the best 3 matches, but omits data freshness, matching logic/thresholds, false-positive behavior, and what happens on no match.

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?

Very short and front-loaded: cost signal first, then the operation, list scope, alias coverage, and return count. Every phrase earns its place with no filler.

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 simple one-parameter tool with no output schema or annotations, the description covers the essential context: it is free, targets one specific Canadian list, includes aliases, and returns the best 3 matches. It could say more about output fields or no-match behavior, but is largely complete.

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 coverage is 0% and the single 'name' parameter is undocumented in the schema. The description compensates by saying it accepts a person, company or vessel name, but does not clarify format (full legal name, partial match, case sensitivity) or whether aliases must be supplied manually.

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?

States a specific verb (screen), resource (person, company or vessel name), and exact scope (Canada's consolidated autonomous sanctions list, SEMA/JVCFOA). The word 'one' implicitly distinguishes it from batch_screen, and regime_list is clearly a different operation.

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?

Implies single-name screening via 'one person, company or vessel name,' which nudges toward batch_screen for bulk use, but does not explicitly name alternatives or state when-not-to-use conditions. 'FREE' is a useful cost signal but not usage guidance.

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