Calculate AIEM (Arbitrio Importación Canarias)

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

Annotations mark it as readOnly, idempotent. Description adds value by explaining AIEM's nature (surcharge on IGIC, for protected industries) and provides an example. 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?

Description is fairly concise, with core purpose upfront. Bilingual format adds length but is appropriate. No wasted sentences.

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?

No output schema, but description explains return fields. Context about AIEM and example aid understanding. Could mention error handling for invalid ncCode, but overall sufficient.

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?

All three parameters have schema descriptions, so baseline is 3. The description adds an example but little else beyond schema. Bilingual text provides minimal extra clarity.

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 calculates AIEM for imports or production in Canary Islands, specifies returns (rate, tax base, amount due), and gives an example. It is distinct from siblings like frihet_tax_id_vies_lookup.

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 use when calculating AIEM surcharge, but lacks explicit when-not-to-use or alternative tools. However, context (Canarian surcharge, protected industries) helps guide appropriate use.

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