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

Annotations already establish read-only, non-destructive semantics, and the description adds real value on top: the 'including Direct Booking' scope, the per-channel-rate capability breakdown (rates/availability/restrictions), the caveat that not every channel rate supports every type, and the auth requirement for a Cotlet API key.

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 with the core purpose and efficient overall, though the opening clause ('Connected booking channels with status and the data each channel rate supports') is partly restated in the following sentence, adding mild redundancy.

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 no-parameter, read-only list tool with no output schema, the description adequately covers what is returned and when to consult it. Return-value detail (exact field shapes) is left implicit, but that is acceptable given the absence of an output 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?

The tool takes zero parameters, so the baseline is 4. The description correctly does not invent parameter detail, and the channel-rate capability caveat gives useful interpretive context for the result set.

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?

States a specific verb and resource ('Returns the channels connected to the property') and enumerates what comes back per channel rate. It orients the agent to a restriction-change workflow, which differentiates it from siteminder_update_restrictions, though no sibling is named explicitly.

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?

Offers a single usage cue — 'check here before a restriction change' — but does not state when-not to use it or name alternatives like siteminder_list_room_rates. The context is implied rather than fully spelled out.

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