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

The annotations already confirm this is a read-only, idempotent, non-destructive, closed-world operation. The description adds substantial behavioral context beyond that: hand-curated provenance with source URL and checked date, a `confidence: "secondary"` marker, yearly review rather than live feed, and an explicit legal-information disclaimer.

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 description is long but front-loads the core purpose and packs in relevant caveats for a tax-data tool: confidence marking, exclusions, review cadence, and disclaimer. Most sentences earn their place, though the volume of caveats makes it less tight than a maximal score would require.

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 output schema exists and annotations cover safety, the description still fills the important contextual gaps: how ranking differs from country lookup, how excluded countries are handled, how secondary sources are flagged, and how often data is refreshed. An agent has enough information to invoke and interpret the tool correctly.

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 description largely restates the schema's own semantics — comma-separated ISO alpha-2 codes, two or more, omit for ranking, and sort is ignored when countries are supplied. It ties parameters to output behavior well, but does not add much syntax or meaning beyond the schema, so the baseline of 3 is appropriate.

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 (compare/rank) and resource (standard and reduced VAT/GST rates by country), with the 41-country spine and source provenance made explicit. It is clear what the tool does, but it does not distinguish itself from nearby siblings such as compare_tax_rates or compare_tax_burden, so it falls short of a 5.

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 describes the two usage modes: pass `countries` to get per-country rates, or omit it to rank standard rates. It also explains how countries without a single national rate are excluded and named rather than assigned a 0%. However, it does not explicitly state when to choose this tool over sibling alternatives, so a 5 is not warranted.

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