suggest_vat_treatment_latam

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

Annotations already declare readOnlyHint=true and idempotentHint=true, indicating no mutations. Description adds that the tool 'suggests' likely treatment and advises verification with a tax advisor, which aligns and provides extra caution. No behavioral 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?

Three sentences plus a disclaimer; each sentence adds value. Information is front-loaded: purpose, inputs, coverage, return structure, use cases, and caveat. No fluff or repetition.

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?

Given the tool's complexity (4 parameters, output schema exists), the description covers input, output structure (referenced as 'Returns {...}'), use cases, and a necessary disclaimer. The output schema obviates the need to detail return fields. All essential information for correct invocation is present.

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 for all four parameters. The description goes beyond by explaining that the tool 'Covers domestic transactions, exports (zero-rated), imports, and cross-border services,' adding context to the operation_type enum values (goods, services, digital_services). This adds meaning 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?

Description clearly states the tool 'suggests the likely VAT/IVA treatment' and lists all input dimensions (seller_country, buyer_country, etc.). The verb 'suggests' is specific, and the resource 'VAT/IVA treatment' is distinct from sibling tools that calculate amounts or retrieve rules.

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?

Description explicitly says 'Use when building checkout tax logic, invoice generation, or cross-border LatAm compliance workflows.' This provides clear context for usage. However, it does not exclude alternatives (e.g., calculate_vat_amount_latam for amounts), so it misses explicit when-not-to-use guidance.

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