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

Annotations already declare readOnlyHint=true, so safety needs no restating; the description instead adds genuinely new behavioral detail — zero-based paging and the 'follow next_page until null' termination loop, which is the only place the next_page cursor is documented since there is no output schema.

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?

Three short sentences, no filler, with the core purpose and pagination loop front-loaded before the routing hint to the search tool.

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 read-only two-parameter lister with full schema coverage, the description covers the only non-obvious behavior — how iteration ends via next_page. It could mention whether an empty page signals exhaustion, but nothing essential to a correct call is missing.

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 both parameters (page, limit) and their bounds/defaults are already fully documented. The description's pagination notes concern traversal rather than parameter meaning, so it adds no semantics beyond the schema — baseline 3.

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 ('List one page of Hub Planner bookings') and immediately scopes it as the unfiltered counterpart to the search tool, so an agent can distinguish it from hubplanner_search_bookings without opening either 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?

Explicitly routes filtered queries to the search tool, giving a clear when-to-use-this-vs-alternative rule. The hedge 'where available' and the absence of any stated prerequisites (auth, workspace scope) keep it short of a 5.

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