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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, so the description correctly spends its words on what annotations cannot say: VIES may be unavailable, invalid numbers surface as errors rather than a negative result, and some countries withhold name/address data. It also tells the agent to confirm the returned entity with the user before proceeding, which is real operational guidance.

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 purpose and the when-to-use condition are front-loaded, and the return/error behavior closes the paragraph. It is a dense single paragraph; a sentence break before the return-value discussion would aid scanning, but no sentence is filler.

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 two-parameter read with no output schema, the description covers everything an agent needs: what it validates, what it returns, the caveat that some fields may be absent, how failures appear, and where the result feeds next. Nothing material is left to inference.

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 is 3; the description goes beyond it by explaining that vatCountry and vatNumber are the values carried forward into the quote and order tools, making their downstream role concrete. It does not restate the formatting rules already in the schema, which is correct.

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 names a specific verb and resource (checks an EU VAT number) and identifies the authoritative backend (the EU's VIES service), plus the business framing ('as the website does before an order'). That is enough for an agent to distinguish it from every sibling, none of which touch VAT.

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 the exact triggering condition ('when a quote adds VAT for an entity in another EU country and the user gives its VAT number'), the outcome of a hit (reverse charge removes VAT), and the follow-up path (pass vatCountry/vatNumber to get_renewal_quote, get_registration_quote, or the order tool). Alternatives and post-conditions are both explicit.

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