UK Tourist Tax (Visitor Levy) Calculator

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds genuinely useful behavioral context beyond that: what is returned (levy, calculation breakdown, return deadline), that the tool is free, and effective-start dates for Edinburgh/Glasgow/Cardiff levies that determine whether a tax applies at all.

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-loads the essential scoping constraint ('UK only') and then packs jurisdiction rates, return contents, and the OTA-liability note into a short block. The rate enumeration is dense but each clause carries decision-relevant information.

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 10 parameters, no output schema, and mutation-free annotations, the description covers what an agent needs: scope, per-booking applicability, output contents including the return deadline, and conditional date-based applicability. Only the sibling relationship/alternative routing is left implicit.

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%, so each parameter is already documented in the schema, including VAT treatment, cleaning fees, and under-18 handling. The description adds area-level rate context but no syntax or semantics beyond the schema; 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?

States a specific verb+resource (calculate UK tourist tax on one booking) and scopes it geographically ('UK only'), then enumerates the jurisdictions and rates it covers. An agent can readily distinguish this from the sibling uk_tourist_tax_rules, which is a rules lookup rather than a per-booking calculation.

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?

Gives clear usage context: applies per booking, UK only, free to call, and explicitly notes the host owes it even when booked through Airbnb or Booking.com. It does not name the sibling tool or state when to prefer rules lookup instead, so it stops short of explicit alternative routing.

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

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description still adds value beyond them with the 'UK only' geographic constraint, the 'Free' cost signal (analogous to rate/cost disclosure), and the enumeration of returned content. It omits data freshness/update cadence for deadlines, which is the one remaining behavioral 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?

Three short sentences, front-loaded with the hard constraint ('UK only') and the returned content, closing with a single-word cost note. No filler and nothing buried.

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, closed-world, read-only lookup with no output schema, the description enumerates the returned fields and both invocation modes, which is enough to call it correctly. It stops short of noting how current the deadline data is or how areas map to the enum values.

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 enum parameter is fully documented in the schema, so the baseline is 3. The description's 'one area, or a list of every area' merely restates the optionality already expressed in the schema ('Optional. Leave out to list every area.') without adding format or selection guidance.

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?

Specific verb ('Returns') plus a concrete resource list: tourist tax rules, start dates, next return deadlines, and Wales registration duty. It also states scope ('UK only') and coverage (one area or all areas). It does not, however, name or differentiate itself from the sibling calculate_uk_tourist_tax, so the boundary between 'rules lookup' and 'tax calculation' is left implicit.

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?

'for one area, or a list of every area' implicitly tells the agent how to use the optional parameter, and 'Free' signals there is no cost barrier to calling it. But there is no explicit when-to-use guidance and no mention of when to prefer the sibling calculate_uk_tourist_tax instead, so usage is inferred rather than stated.

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