update_reservation

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

Annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true) already convey the mutation and non-destructive nature. The description adds no side-effect context: does adding a note append or overwrite? Does updating status trigger notifications? It does not contradict annotations, but it fails to add meaningful behavioral detail beyond the schema.

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, front-loaded sentence that communicates the essential purpose without any wasted words. It is appropriately sized for the tool's complexity.

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?

With 7 parameters and no output schema, the description should clarify that only provided fields are updated, what the return value looks like, and whether partial updates are supported. It also doesn't note that reservationId is the sole required parameter. The description is too sparse for a moderately complex update tool, missing important usage context.

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% — all 7 parameters are described in the schema. The description merely restates categories (status, dates, guest info, notes) without adding new meaning or clarifying edge cases like date formats or allowed status values 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 clearly states a specific verb ('Update') and resource ('reservation details'), enumerating the key fields (status, dates, guest info, notes). This distinguishes it from read-only reservation tools and other sibling tools like get_reservations or search_reservations.

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?

No explicit guidance on when to use this tool versus alternatives such as create_reservation_note (which also adds notes) or update_calendar (which might handle date changes). The context is implied from the name and description, but there are no exclusions or alternative tool references.

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