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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the description does not need to restate safety. It adds useful behavior beyond annotations: results are newest-first, confirmed_at=null means not confirmed, and the guest access secret is never returned.

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 definition is front-loaded and compact, with the core purpose and returned fields stated first. The trailing 'GET /bookings' is mostly redundant, but the rest of the sentences carry useful information.

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 list endpoint with no output schema, the description gives enough context about fields, sorting, filtering, null confirmation meaning, and related resources. It does not explain pagination response details, though the offset parameter description partially covers that.

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 parameters are already well documented. The description reinforces that filtering is available by creation date, confirmation state, or reference text, but it does not add syntax or semantics beyond what the schema already 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?

The description states a specific verb and resource: list bookings, newest first. It also names the key returned fields and clarifies that booking dates and guests live on calendar events, which distinguishes this list operation from related booking/contact/calendar tools.

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?

It clearly says to use this tool for filtering by creation date, confirmation state, or reference text, and it redirects date/guest detail to bookingmood_list_calendar_events and contacts. It stops short of explicitly naming when not to use this tool versus bookingmood_get_booking, but the list-vs-retrieve distinction is strongly implied.

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