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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the bar is lower; the description still adds real behavioral signal by disclosing that this returns the 'whole page text' — a potentially large payload — plus booking/contact guidance. It omits any caveats on response size, invalid ids, or truncation.

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?

A single dense sentence with the highest-value content front-loaded ('One offering in full') and no filler. Every clause contributes either payload scope or a downstream action.

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 and a single required parameter, the description carries the burden of describing returns and does so concretely (structured fields, full text, plan, inclusions/exclusions, booking path). It stops short of stating failure behavior for unknown ids or response-size expectations for a 'whole page text' payload.

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?

One parameter with 100% schema description coverage, including accepted id formats and URL forms, so the schema carries the semantics entirely. The description adds nothing about the id beyond what is already structured, which is the expected baseline.

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 the specific resource (one offering) and enumerates the payload it returns: structured fields, full page text with day-by-day plan, inclusions/exclusions, and booking instructions. The phrase 'in full' implicitly contrasts it with list_offerings/search, though the verb (retrieve by id) is implied rather than stated.

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?

Usage is only implied: an agent can infer this is the detail lookup for a single offering referenced by search or list_offerings, but the description never says when to prefer it over those siblings or what conditions exclude it. The id-origin guidance ('from search or list_offerings') lives in the schema, not the description.

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