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

Annotations already establish read-only, idempotent, non-open-world, non-destructive behavior, so the description's job is extra context — and it delivers the important part: results are tagged verified/inferred/announced, meaning some rates are unconfirmed, and each carries source links and dates. That provenance and confidence signal is genuinely decision-relevant and appears nowhere in the structured fields.

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?

One front-loaded sentence that opens with the resource and then spends its length on a dense, useful enumeration of what comes back. Slightly list-heavy and lacking a stated verb, but every clause carries information and there is no 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?

An output schema exists, so return shape need not be spelled out; the description instead conveys the semantic dimensions of the payload (jurisdiction, legal basis, validity, confidence). Combined with a fully specified single parameter and clear safety annotations, an agent has what it needs — the missing piece is only the routing rule against tourist_tax.

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% and the single 'place' parameter is fully documented with concrete examples, so the baseline is 3. The description adds only the 'researched place' framing, no additional syntax, normalization, or fallback behavior for unknown places, so it neither compensates nor detracts.

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 a precise resource — every tourist-tax rule for one place — and enumerates the fields bundled into it (rates by stay type, season, area, caps, exemptions, payment, validity, status). That is far more specific than the sibling names tourist_tax or list_places imply, but it never states the verb of retrieval or explicitly contrasts itself with tourist_tax, so the boundary with that sibling stays blurry.

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?

There is no when-to-use / when-not-to-use guidance and no alternative named. The phrase 'one researched place' and the schema hint ('or any town') imply coverage scope but not routing; an agent cannot tell from this text why it should pick place_rules over tourist_tax or list_places.

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