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

Annotations only supply destructiveHint=true and a title; the description adds that this is a write ("MUTATES OwnerRez data"), the exact endpoint and method, and that it returns the created booking. It does not disclose permission requirements, idempotency, or whether a created booking can be undone, which would be valuable for a destructive mutation.

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 tight sentences: mutation flag first, endpoint second, semantics/fallback last. Every sentence carries load and there is no filler.

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 destructive creation tool with a nested `fields` object and no output schema, the description covers the return value ("Returns the created booking") and explains how to handle account-specific payload gaps. It stops short of permission/auth or error behavior, which is a minor gap given the 100% schema coverage.

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 coverage is 100%, so all eight parameters are already documented in the schema (including `fields` being merged into the write body). The description adds the useful note that charge/quote shape is account-specific, but otherwise adds little beyond what the schema states. Baseline 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?

States a specific verb and resource ("creates a new booking (reservation)"), plus the underlying API call POST /v2/bookings. The "booking ties a guest to a property for a date range" clause distinguishes it from siblings like create_guest and create_quote without requiring schema inspection.

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?

Usage is implied: this is the creation counterpart to update_booking/get_booking and the alternative to create_quote. However, it never states explicitly when to choose this over create_quote (quote-then-book flow) or when a booking should be updated instead. The `fields` guidance is parameter advice, not tool-selection guidance.

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