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

The description adds substantial behavior beyond the annotations: it explains the result ordering (restricted first, then unchecked, then clear), how invalid codes are handled via summary.invalid_hs and excluded from counts, and what details are returned for restricted codes. This is strong disclosure for a read-only, idempotent lookup 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 front-loaded with the core action and batch scope, then moves efficiently through output contents, ordering, invalid handling, usage timing, and limitations. Every sentence contributes useful information without repetition.

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?

Although there is no output schema, the description explains the relevant return structure, ordering, and invalid-code reporting, which is exactly what an agent needs for this batch lookup. The annotations cover safety and idempotency, and the schema covers parameter details, so the definition is complete for its complexity.

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%, so the schema already documents hs_codes and direction fully. The description reinforces the 100-code limit and mentions invalid code handling, but it does not add meaning for the direction parameter or explain HS code formatting beyond what the schema provides, so the baseline of 3 applies.

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 a product catalog for Korean import restrictions. The batch scope is explicit through 'in one call' and 'up to 100 HS codes', which distinguishes it from the singular check_korea_import_requirements sibling.

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 gives clear usage context: use before opening a Korea shipping lane or listing a catalog for Korean buyers, and adds the important limitation that this is fact lookup only, not a legal customs determination. It does not explicitly route single-code checks to the non-batch sibling, so it falls short of full when-to-use/when-not guidance.

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