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

With no annotations, the description carries the full burden and does well: it discloses API-key requirements, return contents (cited HTS codes, modifying/revoking rulings, CBP link), coverage metadata, and important legal caveats. It does not cover rate limits or pagination behavior, but the behavioral disclosure is otherwise strong.

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 dense and front-loaded: access requirement first, then the core search operation, return details, coverage metadata, and legal caveat. Every sentence adds useful context without 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?

It covers authentication, operation, return content, and legal caveats, which is valuable given no output schema. But with five parameters at 0% schema coverage, missing limit/offset/collection semantics leaves clear gaps 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 0%, so the description must compensate, but it only explains the hts and query criteria. It leaves limit, offset, and the collection enum (NY/HQ) undocumented, and its hts guidance (4 to 10 digits) is narrower than the schema pattern (4 to 13 characters allowing dots).

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: searching CBP CROSS rulings by HTS code/prefix and/or subject words. It is clear what the tool does, but it does not explicitly differentiate itself from the sibling get_ruling or search_tariffs tools.

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 explains the search criteria and the API-key prerequisite, which implies when to use it. However, it does not state when to use this tool instead of get_ruling or search_tariffs, so guidance is only implicit.

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