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

Annotations already cover read-only, idempotent, non-destructive and open-world behavior, yet the description still adds substantive context: what each entry returns (list name, start date, evidence type and text, matching CAC record IDs), how the two US regimes differ (export-licence vs investment ban), and explicit caveats that it does not resolve corporate identity and that absence from a list is not a clearance.

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?

Purpose and query mode are front-loaded in the first two sentences, and the rest is layered supporting context. It is longer than typical and the DHS DeepSeek order and MORVS disclaimers sit slightly off the core task, but each sentence carries information an agent would otherwise have to guess.

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?

With no output schema, the description carries return-value burden well by enumerating the fields per entry, and it preempts the two most likely misinterpretations (regime conflation and 'not listed = cleared'). It does not mention result-count limits, pagination, or what happens when q is omitted, which for an optional-parameter tool is a real gap.

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 100% and both parameters are documented in the schema, so the baseline is 3. The description goes beyond the enum by explaining the evidentiary meaning of tiers A and B and the consequence of tier B falling outside headline counts, which the schema does not convey.

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 opening sentence gives a specific verb and resource: a curated crosswalk from CAC filer legal names to the US Entity List and Treasury NS-CMIC list. This is clearly distinguishable from siblings such as sanctions_check, watchlist, and china_ai_filings, which an agent could otherwise confuse it with.

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?

It states the query mode (Chinese or English entity-name substring) and that tier defaults to A, and it explains what each tier means and which one belongs in headline counts. It stops short of explicitly naming an alternative sibling tool or stating when-not-to-use, though the pointer to 'the separate US actions timeline' gestures at routing.

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