trade.tariff

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

With no annotations, the description carries full burden. It describes returns for each mode: for code, 'line + 10-digit stat suffixes with duty rates'; for query, 'ranked candidate HS codes by hierarchical heading'. It also mentions data size and source, providing good behavioral context.

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 concise at two sentences, front-loaded with the main purpose, and every sentence provides essential information without redundancy.

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?

Without an output schema, the description adequately explains the return types for both modes and mentions the data source. It could be improved by including error handling notes, but overall it is sufficiently complete for a lookup tool.

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?

Although schema coverage is 100% and parameter descriptions exist, the tool description adds value by explaining how each parameter affects the output. For example, it states that using 'code' returns stat suffixes with duty rates, while 'query' returns ranked candidates. This context enriches the schema descriptions.

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 states the tool does 'Look up or search the US Harmonized Tariff Schedule (HTS / HS codes)', specifying two modes: exact code lookup and free-text search. It differentiates itself from sibling tools by being the only tariff-specific lookup tool.

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 when to use each mode: 'Pass code for an exact HTS number' and 'query for free-text → ranked candidate HS codes'. It provides clear context but does not explicitly state when not to use the tool or mention alternatives.

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