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

readOnlyHint already declares this a safe read, yet the description adds real context: default newest-first ordering, cursor semantics for afterId, and the caveat that dateType "only on accounts with the new reservations query." It stops short of mentioning auth needs or result caps.

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 purpose, then filters, then pagination and lookup data. Every clause serves a purpose, though the long channel-id enumeration makes it denser than ideal. No filler sentences.

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 23-parameter, zero-required list tool with no output schema, the description covers what is returned, how to filter, ordering, and pagination. Auth/error behavior is omitted, but that is a minor gap given the read-only annotation.

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%, so baseline is 3, but the description adds the channel-id legend (2000 direct, 2018 airbnbOfficial, 2002 homeaway/Vrbo, ...), which the channelId property schema does not provide. That is genuine meaning beyond the structured field.

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 ("List reservations") and enumerates the payload shape (guest, dates, status, price, channel), so the agent knows exactly what comes back. The "across all channels" scope plus the endpoint reference cleanly separates it from the get_reservation/update_reservation siblings.

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?

States the filtering dimensions (listing, channel, arrival/departure window, guest name/email, unread messages) and gives concrete pagination guidance ("for large accounts page with afterId"). No explicit when-not or named alternative, but the usage context is unambiguous.

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