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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so safety is covered. The description contributes the state constraint that results are only unbooked drafts, but says nothing about pagination behavior or the return shape.

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?

A single short clause with no filler. It is appropriately sized for a simple query tool, though the fragment style means the action is never stated outright.

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 zero-required-parameter list tool with full annotation coverage and no output schema, the description is minimally adequate. It omits pagination semantics and what a draft record contains, which an agent would want before paging or interpreting results.

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?

The schema documents all three parameters (limit, cursor, search) at 100% coverage, so the schema does the heavy lifting. The description adds no detail on filtering by customer, page size, or cursoring, so the baseline of 3 applies.

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 the resource ('draft bookings and quotes') and adds a meaningful definitional constraint — they are 'not yet booked' — but it is a noun fragment with no verb, so the listing action comes only from the tool name. It does not distinguish itself from siblings like list_bookings or get_booking beyond the word 'draft'.

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?

There is no statement of when to use this tool versus list_bookings, get_booking, or send_quote, and no guidance on paging through results. The agent must infer the choice from the name alone.

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