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

Annotations already cover readOnly/idempotent/closed-world, so the bar is lower, and the description adds genuinely new behavioral facts: a per-call price ($0.001 USDC), the payment rail (x402, Base mainnet), and that results include notes on slabs, reduced rates and temporary cuts. It stops short of describing response shape or whether rates are cached/dated, which matters for tax figures.

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?

Front-loaded with what the tool returns, then scope, then cost — good ordering, and the country/slab enumeration is efficient evidence of coverage. It does partly duplicate the title's country list (India, Indonesia, UAE, Saudi Arabia, Japan appear in both) and the price sentence could be tightened, but nothing is seriously wasteful.

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 one-optional-parameter lookup with annotations and no output schema, the description covers scope, sample values, extra detail returned (slabs, reduced/temporary rates), and cost. The main remaining gap is that an agent cannot predict the response payload structure, which matters since no output schema exists to explain it.

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 description coverage is 100% and the single 'country' parameter already documents itself as optional comma-separated 2-letter ISO codes defaulting to all 39. The description's 'Filter by ISO country codes' restates that rather than adding format or edge-case guidance, so the baseline 3 applies.

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?

Names the exact resource (standard GST/VAT/sales tax rates), the exact coverage (39 countries in Asia and the Middle East) and gives concrete sample values (India 18%, UAE 5%, Saudi Arabia 15%). This clearly separates it from the sibling africa_vat_rates and asia_central_bank_rates without needing to open the schema.

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?

It states intended applications ('pricing, invoicing and cross-border e-commerce') and the filtering mechanism, which implies when to reach for it. However, it never names an alternative or an exclusion — e.g. when to use africa_vat_rates instead, or how it relates to exchange_rates for cross-border pricing — so the routing decision is left partly to inference.

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