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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered elsewhere. The description adds useful scope information — that this returns the *full public text* across several page types plus the canonical URL — but says nothing about failure behavior for bad ids, redirects, or truncation of long pages.

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 front-loaded sentence that leads with the return value and uses the parenthetical to enumerate page types. No filler, no repetition of the title, and every clause carries 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?

For a one-parameter, idempotent read with a fully documented schema and no output schema, the description gives enough to call it correctly: what comes back, in what shape (text plus URL), for which page families. The remaining gap is the unresolved overlap with get_offering, which an agent would still have to guess about.

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 id parameter already documents the accepted formats (journeys/..., retreats/..., blog/<slug>, or a full URL). The description's reference to 'one page' and the content types only loosely echoes that, so it adds little beyond the schema — the baseline of 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?

The description names the resource precisely and enumerates the content it returns (journey itinerary, retreat programme, inclusions, guest care, blog article card) plus the URL. The verb is carried by the name/title rather than the description, and the boundary with the sibling get_offering is not drawn, 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?

There is no statement of when to call this instead of get_offering, search, or list_offerings, even though get_offering is a close-sounding sibling that an agent could easily pick by mistake. The only usage signal ('one page', 'full public text') is implied rather than stated, and no exclusions or prerequisites are given.

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