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

With no annotations, the description carries the transparency burden and does well: it discloses the source (USITC HTS REST API), refresh cadence (daily), the specific data returned, and the caveat that the output is only candidates requiring verification on USTR. It does not cover failure modes or rate limits, but for a lookup tool this is solid.

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?

Two dense sentences with the core purpose front-loaded, followed by the data contents and the critical non-ruling caveat. No filler or repeated schema information.

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 no output schema and no annotations, the description explains enough: source, daily refresh, returned fields, and interpretation caveat. It is slightly light on output structure and how the two optional parameters interact, but the schema covers parameter semantics and the tool is simple.

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 the description adds no parameter-level detail beyond the schema. It mentions 'product category' but does not explain how pick/query select or combine; baseline 3 is appropriate because the schema already documents both parameters.

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 clearly identifies the tool as providing candidate HTS headings for a consumer product category, with a specific data source and contents (candidate line, general rate, rated lines, Section 301 status). It explicitly distinguishes itself from a classification ruling, which separates it from the classification_rulings 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 context for use: look up candidate HTS headings pulled daily from USITC, and explicitly says these are not a classification ruling and the importer of record classifies. It does not name sibling tools as alternatives (e.g., classification_rulings for final rulings), so it stops short of full when/when-not routing.

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