calculate_tariff

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

Given no annotations, the description details the multi-layer tariff computation, projected rates after a specific date, and optional dollar impact. It does not cover error handling or auth, but the computational behavior is well described.

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 a single, well-structured paragraph that front-loads the core purpose and then lists outputs and parameter details. Every sentence provides value with no 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?

The description explains the return structure thoroughly even without an output schema. Minor omission: no mention of error conditions or validity checks for HTS codes, but overall sufficient for a calculation 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?

Schema coverage is 100%, so baseline 3. The description adds meaningful context: HTS code format flexibility (dots ignored), default country, and the effect of the optional import value parameter on response. This exceeds the schema alone.

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 explicitly states the tool calculates 'full stacked US import tariff rate' for a given HTS code and origin country. It lists the return components and optional dollar impact, clearly distinguishing it from the sibling lookup_hts_code.

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 tool is for tariff rate calculation but provides no explicit guidance on when to prefer it over lookup_hts_code or what prerequisites exist. The agent must infer usage from the description alone.

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