getHotelTaxSchema

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description still adds real behavioral value beyond that: fixed amounts are USD, percentages apply to the room rate (13.5 = 13.5%), and the schema is produced by an offline pipeline, so hotels without learned data return 404.

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-loaded Overview followed by tightly scoped sections; each bullet earns its place. It is slightly longer than strictly necessary for a one-parameter read tool, but there is no filler or repetition.

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 no output schema, the description carries the burden of describing the return shape and does so: each entry states inclusion in the rate, percentage vs fixed, and fixed-amount scaling. It also discloses the 404 case. Missing only a full top-level response envelope description.

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% for the single hotelId parameter, and the schema already documents the 'lp' or numeric identifier format. The description never mentions hotelId, so it adds nothing beyond what the structured field provides — baseline 3.

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?

Opens with a specific verb + resource ('Returns the tax schema of a hotel') and immediately distinguishes the payload as normalized, provider-independent static data. That normalization framing is enough to separate it from sibling catalog tools like get_data_hotel without opening either 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?

The 'When to Use' section gives three concrete scenarios (price transparency, amount-due-at-property estimates, tax auditing) that make the invocation context clear. It does not name alternatives or state when not to use it, so it stops short of the top band.

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