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

The description adds meaningful methodological context by mentioning HTS base rates and Chapter 99 measures, and claims the results are transparent and rule-based. However, with annotations limited to openWorldHint, the description does not disclose important behavioral details such as data mutability, recency of tariff data, unsupported countries, or failure behavior.

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 core functional description is concise and front-loaded in a useful way. The pricing note is relevant operational context, although it could be considered slightly out of place inside the behavioral description. Overall it earns its place with no unnecessary fluff.

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 2 required parameters and output schema, the description is mostly sufficient. However, the existence of tariff_classification as a sibling suggests the description would benefit from an explicit cross-reference or workflow hint, especially because product_description can be free-form instead of an exact HS code.

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%, and both parameters already have clear descriptions. The tool description does not add any extra interpretation or guidance beyond what the input schema already provides, so it stays at the baseline of acceptable.

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 action ('Calculates U.S. customs duties') and identifies the exact method ('combining HTS base rates with applicable Chapter 99 measures'). This clearly differentiates the tool from the sibling tariff_classification, which presumably handles classification rather than duty calculation.

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 implies the intended use: calculating duties for imports into the U.S. However, it does not explicitly explain when to use tariff_calc versus tariff_classification, nor does it address input readiness issues such as the need for an HS code or what to do if the description is too vague to classify or calculate.

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