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

Annotations already indicate the operation is not read-only, not idempotent, and not destructive)Skip the description adds valuable context: the hold is temporary, expires automatically, and blocks other customers or assistants for 15 minutes. This goes beyond what the annotations can convey.

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 deliver the key facts up front: what the hold does, its duration, its exclusivity, automatic expiry, and when to call. No filler or repetition of schema details.

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?

The description is complete for an agent deciding whether and when to call. It explains the purpose, duration, expiration behavior, and relationship to the booking flow, while the output schema handles return details.

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 67%, with pickup_date and pickup_time already documented with formats and timezone. The description does not explicitly explain how quote_id maps to the 'quoted date' it mentions, leaving quote_id somewhat underspecified beyond its name.

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: 'Temporarily reserves the quoted date for THIS customer for 15 minutes.' It clearly distinguishes itself from create_booking by explicitly saying 'Not a booking,' and the exclusivity detail removes ambiguity about what the hold accomplishes.

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?

Provides explicit when-to-use guidance: 'Call after availability is confirmed and the customer wants to proceed.' It also communicates what this tool is not for with 'Not a booking,' which helps the agent avoid using it as a final booking operation.

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