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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new context: hard limits (3 properties, 4 cards/page, 60 offers), that it rechecks availability for authoritative totals, that it 'never accepts prices or quote data', and that it performs no bookings/holds/quotes/payments. This is useful behavioral disclosure beyond the annotations.

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?

The scoping statement is front-loaded, but the text is a dense run-on with real redundancy: 'data-only' appears twice, show_available_rooms is explained twice, and 'never accepts prices or quote data' overlaps with 'No bookings, holds, quotes, emails or payments.' Several sentences could be merged without losing meaning.

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 values need no explanation, and annotations cover safety. The description supplies limits, prerequisites, sibling routing, and negative exclusions, making it largely complete for a nested-object pagination tool. Minor gaps remain around offset/children semantics, which are neither in the description nor the schema.

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 only 25% across 8 parameters, so the description carries some burden. It adds meaning for selections (property/room/rate/count IDs), and the need to preserve exact dates, guests, budget, and display currency, plus the 3-property/4-card/60-offer caps. However, it does not explain offset pagination or children, leaving notable gaps relative to the low schema coverage.

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 states a specific verb+resource: reading a page of room comparison cards inside an already mounted comparison. It explicitly differentiates itself from sibling show_available_rooms ('data-only for mounted-card pagination' vs 'renders once'), so an agent can distinguish them. The 'mounted comparison' framing is jargon-heavy but still conveys the operation.

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?

It names the alternative (show_available_rooms) and the condition that selects it ('For initial presentation'), plus an explicit prohibition ('do not page this tool to assemble Markdown thumbnails'). It also gives the prerequisite workflow ('First search availability, then select returned property/room/rate/count IDs'), leaving little to inference.

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