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

The readOnlyHint annotation already signals a safe read operation. The description adds useful context beyond the annotation: the exact HTTP endpoint (GET /v2/bookings) and the shape of the paginated response. It stops short of mentioning rate limits or auth requirements, but provides solid behavioral detail.

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 description is short, front-loaded with the core purpose, and then efficiently covers API endpoint, filters, and return shape. Every sentence earns its place with no 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 list tool with 13 optional parameters and no output schema, the description provides the endpoint and return shape, which is enough to invoke correctly. It omits details about the generic `params` object and pagination semantics, but the schema covers parameter-level specifics.

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 100%, so the schema already documents all 13 parameters in detail. The description summarizes filter categories (property, date range, changed-since, status) and optional includes, which adds some framing, but does not explain syntax, constraints, or the generic `params` object beyond what the schema provides.

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 ('List') and resource ('bookings (reservations)'), and names the API operation. The verb clearly distinguishes it from sibling tools like get_booking, create_booking, and update_booking.

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 explains what can be filtered and embedded, which implies typical usage. However, it does not state when to use this tool versus alternatives such as get_booking or list_payments, nor does it provide any exclusions.

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