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

The annotations already declare readOnly/openWorld/non-destructive, so the description's added value is the coverage limits: non-EU countries return only standard rates, while historical and postcode-level data require a paid plan. It also discloses a concrete cost (2 credits). It does not describe behavior on an invalid or unsupported country code, which is the main remaining gap.

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?

It is front-loaded with the core action and coverage, with cost appended at the end as a clear tag. The only waste is the redundant 'VAT Rates: VAT Rates' opening that restates the name/title twice before any substantive content.

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?

With an output schema available and 100% schema coverage on all three parameters, the description only needs to carry scope, cost, and feature gating, which it does. A brief note on unsupported country codes or error behavior would make it fully complete, but nothing essential is missing for correct invocation.

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%, so the baseline would be 3, but the description adds meaning the schema does not: the date parameter yields historical rates and postcode yields regional exceptions, and both are gated behind paid plans. That qualification is genuinely useful for deciding whether to pass those parameters at all.

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 states a specific verb and resource ('send a two-letter country code and get the current VAT rates ... as JSON') and pins the scope precisely: full rate tiers for EU members plus the UK, standard rates only for non-EU countries. That scope statement is what separates it from siblings like SalesTaxLookup/CurrencyRate, so an agent can choose it without opening 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 clearly establishes the context of use (European VAT by country code) and explains when the optional parameters matter: historical rates by date and regional exceptions by postcode, both tied to paid plans. It stops short of naming an alternative tool or stating when not to use it, so there is no explicit exclusion guidance.

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