uk_duty_calculator

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

Annotations already indicate read-only, non-destructive, idempotent behavior. The description adds context about using live GOV.UK data, calculating CIF, and applying duty/VAT sequentially. It doesn't mention limitations like data freshness or error handling, but the added detail is sufficient.

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 with a clear opening sentence, a brief explanation of the calculation, and a bulleted list of use cases. No unnecessary words; each sentence adds value.

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?

For a calculator tool without an output schema, the description explains the calculation steps but does not explicitly list the output fields (e.g., duty amount, VAT, total). However, the purpose and process are clear enough for an agent to infer the expected return values.

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% with descriptions. The description adds meaning by explaining how parameters contribute to the CIF calculation and duty/VAT application, providing context beyond the schema.

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 it estimates UK import duty and VAT for any commodity code, using a specific verb+resource. Among sibling tools, none appear to cover duty/VAT calculation, making its purpose distinct and well-defined.

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 tool provides a list of explicit use cases (estimate import costs, check duty rates, etc.). It does not mention when not to use, but the listed scenarios are clear and cover common needs. Alternatives among siblings are not discussed, but the purpose is specific enough.

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