Calculate AIEM (Arbitrio Importación Canarias)

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds value by explaining the nature of AIEM (surcharge, protected local industries) and confirming it returns rate, base, and amount. No contradictions.

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: two sentences, an example, and bilingual text. It front-loads the purpose and adds necessary context without superfluous words.

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 calculation tool with three parameters and no output schema, the description fully explains what AIEM is, what is returned, and provides a working example. It is complete for an agent to understand how to use it correctly.

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 covers all parameters with descriptions (100% coverage). The description provides an example mapping ncCode='8471', amount=1000, and description text, which adds practical clarity beyond what the schema offers.

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 calculates AIEM for goods imported to or produced in the Canary Islands, specifying the verb 'calculate' and the unique resource (AIEM tax). It distinguishes itself from sibling tools by focusing on this specific tax calculation, which no other sibling addresses.

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 that AIEM is a surcharge on IGIC for protected local industries, providing context for when this tool is appropriate. However, it does not explicitly state when not to use it or mention alternative tools, but the clarity of the domain makes usage clear.

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