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

Annotations only declare destructiveHint=true; the description adds real behavioral context: it is a mutation, it uses PATCH /v2/bookings/{id}, and critically that only included fields change (partial-update semantics). It does not cover auth requirements, rate limits, or reversibility, but goes well beyond the annotation.

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?

Compact and front-loaded with the mutation warning and endpoint; the passthrough guidance follows. Dense but every clause earns its place, with only mild compression into a single long line.

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 mutation tool with no output schema and 100% schema coverage, the description covers the essential behavioral facts (endpoint, partial-update semantics, flexible field passthrough). It omits auth/error handling, but nothing needed to invoke the tool correctly is missing.

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 already 100%, so the baseline is 3, but the description adds meaning by explaining that `fields` is merged with the typed fields and can carry any documented OwnerRez field, and by enumerating field categories (dates, guest counts, notes, status).

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 ('updates an existing booking') and flags the mutation nature immediately with 'MUTATES OwnerRez data'. This clearly distinguishes it from siblings like create_booking and get_booking.

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 useful mechanics — PATCH semantics and the `fields` passthrough for any documented field — but offers no guidance on when to use this versus the generic `ownerrez_request` sibling or update_guest. Usage is implied rather than stated.

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