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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false. The description adds useful behavioral detail beyond that: default newest-first ordering, pagination via `next`, the endpoint (GET /bookings), and a summary of returned booking fields including customer notes, questions and statuses. It does not cover auth, rate limits or response envelope details.

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 compact sentences, front-loaded with the core action and default order. Every clause carries useful information about filtering, response shape or pagination.

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?

With no output schema, the description usefully describes what each booking contains (service, resource, start/end, status, customers with notes/questions/statuses), which is essential for an agent calling the tool. Pagination and default sort are also covered. Some structured parameter details remain schema-only, appropriately so.

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 18 parameters thoroughly. The description groups the filterable dimensions, which is helpful for orientation but adds little specific parameter semantics 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 and resource ('List bookings') and immediately establishes the default ordering ('newest first by default'). No sibling tool competes for booking listing, so the purpose is unmistakable.

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?

Gives clear filtering context across time, customer, service, resource, category, status and creation/update time, plus pagination guidance ('Page with `next`'). It stops short of explicit when-not-to-use or alternative-tool exclusions, but for a general list endpoint the usage is well framed.

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