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

Annotations already declare read-only, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine context beyond that: the sort order, the implicit date window, the implicit exclusion of cancelled bookings, and the fact that draft-preview test bookings are hidden by default. It still doesn't say anything about result limits or pagination.

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 dense sentences, with the scope and sort order front-loaded and defaults immediately after. Every clause carries information; only the parenthetical is slightly bumpy to parse.

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 not be described. For a five-parameter list tool with annotations covering safety, the description supplies the behavioral defaults an agent needs to call it correctly and interpret the result set scope.

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 60%, so the description safely carries extra weight. It explains what the implicit defaults mean for 'from'/'to' (now through 60 days) and that 'status' defaults to non-cancelled, and it clarifies the practical effect of 'tests' values ('include' or 'only' let draft test bookings through) beyond the bare enum in the schema.

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 names a specific resource (bookings) scoped to a site and states the sort order, 'soonest first'. It does not name a sibling it is distinct from, but the resource is unambiguous among the list_* tools, so an agent can identify it without opening the schema.

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 default window (from now, next 60 days) and the default status filter imply the intended use case: upcoming bookings. However, no explicit when-to-use or when-not guidance is given, and no alternative tool is suggested for past bookings or for finding a single booking.

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