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

Annotations already establish that the operation is read-only, idempotent, and non-destructive. The description adds meaningful behavior beyond that: results are paginated ('bounded page'), scoped to one hotel, and deliberately exclude channel-manager mappings, integration metadata, and credentials. This tells the agent what it will not find in the response.

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?

Two sentences, no filler, and the primary scope is front-loaded. The first sentence delivers the action, resource, scope, and pagination; the second adds the critical exclusions. Every clause earns its place.

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 simple read-only list endpoint with an output schema and safety annotations, the description is nearly complete: it identifies the resource, scope, pagination, and exclusions. It does not explain roomTypeId filtering or pagination defaults, but the schema and output schema fill most of the remaining operational detail.

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 description coverage is only 25%, so the description carries some burden. 'Bounded page' partially conveys limit/offset semantics and 'one organization-owned hotel' clarifies hotelId, but roomTypeId receives no semantic explanation in the description. The gap is clear, though the parameter names are reasonably self-descriptive.

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 uses a specific verb and resource: 'List a bounded page of rate-plan pricing configuration for one organization-owned hotel.' This clearly distinguishes it from sibling list tools by scope ('one hotel') and content ('rate-plan pricing configuration'), and the second sentence states what is excluded, further sharpening the boundary.

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?

The description implies usage context: it is for a single organization-owned hotel and returns a bounded page of rate-plan pricing. However, it does not explicitly state when to prefer this over the closely related sibling list_daily_rates, nor does it name any alternative or exclusion condition for tool selection.

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