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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds real behavioral context the annotations do not: which result fields come back, that some everyday terms are auto-mapped to HTS wording, and that this mapping is surfaced in the response — useful for interpreting surprising matches.

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?

A single dense sentence front-loads the verb and resource, then enumerates the returned fields with no filler. It is long but every clause carries information; only the closing mapping note could arguably be tightened.

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 does the work of explaining return contents, which it handles well for a three-parameter search tool. Minor gaps remain: no mention of what happens when nothing matches, no result ordering or truncation behavior, and Chapter 99 filtering is left entirely to the schema.

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 100%, so all three parameters are already documented, including limit bounds and the Chapter 99 flag. The description reinforces that 'keyword' means product words and notes the everyday-term mapping layer, but adds no syntax, matching rules, or guidance about when to set include_chapter_99 — the baseline 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 gives a specific verb ('Searches') and resource ('descriptions in the current Harmonized Tariff Schedule of the United States'), plus the exact output shape: 8- and 10-digit HTS lines with code, description, parent headings, duty rate and unit of quantity. That makes the keyword-driven nature clear enough to separate it from a code-lookup sibling such as hts_rate, though no sibling is named explicitly.

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?

Usage is only implied: the agent can infer this is for product-word searches against HTS text rather than retrieval by code, and the example terms (laptop, drone, e-bike) hint at the intended query style. There is no explicit statement of when to prefer this over hts_rate, nor any exclusion or prerequisite.

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