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

Annotations already cover the safety profile (readOnly, idempotent, openWorld), and the description adds genuine behavioral context beyond them: ancestry is computed from the whole containing heading before filtering, section titles live in a separate 'sections' field outside legal ancestry, and chapters 98/99 preserve published forest roots without inventing four-digit records. These are non-obvious semantic rules an agent could not get from annotations or schema.

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 what-is-it sentence is front-loaded, and each subsequent sentence carries a distinct fact (ancestry construction order, section titles, nodeId follow-ups, chapter 98/99 edge case). It is dense with domain jargon ('published forest roots', 'unnamed superior rows') that an unfamiliar agent may find opaque, but nothing reads as 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?

An output schema exists, so return values need no explanation, and the description instead covers the non-obvious edge cases (whole-heading ancestry, section titles kept separate, chapter 98/99 roots). Together with a fully documented 4-parameter schema and safety annotations, this is sufficient for correct invocation.

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 the schema already documents code, limit, cursor and nodeId thoroughly; the baseline is 3. The description adds some meaning to nodeId via the 'exact nodeId follow-up' note, but it does not explain the dotted/bare code convention or limit behavior beyond what the schema states.

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 opens with a specific verb and resource ('Inspect a four-, six- or eight-digit HTS classification and its complete indented descendants'), which clearly separates it from a flat search tool. It never names the sibling tools (e.g. usitc_browse_chapter, usitc_search_hts), so an agent still has to infer the boundary itself.

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 by the phrasing: 'omit to browse' (on nodeId) and 'Each parent and inherited-rate source has an exact nodeId follow-up' hint at drill-down behavior, but there is no explicit when-to-use versus search_hts or browse_chapter. No exclusions or prerequisites are given.

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