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

Annotations already mark this as read-only and idempotent, but the description adds useful domain-specific behavior: Chapters 98 and 99 expose actual published entries, grouping depends on sourced markers, and reserved chapters can return a successful empty collection. The wording is dense, but the extra behavioral context is substantive and does not contradict the annotations.

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 reasonably short and starts with the browse action, but it is written as a dense run of domain jargon rather than clearly structured guidance. The edge-case sentences earn their place, but the overall phrasing is harder to parse than necessary.

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 the existing output schema and complete parameter schema, the description supplies the main non-obvious behavioral caveats an agent would need. It does not cover routing among siblings, but for calling the tool correctly the edge-case coverage is fairly complete.

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 chapter, limit, and cursor are already well documented in the schema. The description does not add parameter-specific semantics beyond what the schema provides, making the baseline 3 appropriate.

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: browsing numbered headings, with rate-line and statistical-count details. It is clear enough to identify this as an HTS chapter browsing tool, but it does not explicitly differentiate the tool from siblings such as usitc_get_heading or usitc_search_hts.

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?

The description gives no explicit guidance on when to use this tool versus the sibling lookup/search tools. It mentions edge cases like Chapters 98 and 99 and reserved chapters, but those are behavioral notes rather than selection guidance.

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