PATCH /room/booking/:id (Conexa Coworking > Booking)

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

Annotations already indicate readOnlyHint=false (write) and destructiveHint=false. The description adds the list of editable fields but does not disclose any side effects (e.g., whether updates trigger emails despite email flags) or constraints like partial update behavior. It relies on annotations for basic transparency, so a 3 is appropriate.

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?

The description is concise, with a clear opening sentence and a bullet list of body fields. It is well-structured and avoids unnecessary verbosity, though it could benefit from grouping related fields.

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 lists editable fields but lacks information about update behavior (e.g., partial update, required fields, error handling, return format). No output schema is provided, so the description should have explained response details. It leaves significant gaps for an update tool.

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% for id and body parameters, but the description adds significant value by detailing the expected fields inside the body object (e.g., personId, date, startTime, visitors with subfields). This compensates for the body schema's generic additionalProperties.

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 it edits fields of a room booking ('Edição de campos de uma Reseva de Sala de Reunião'). It is specific about the resource and action, though it could explicitly mention it updates an existing booking to differentiate from create_room_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?

No guidance is provided on when to use this tool versus alternatives like create_room_booking, cancel_room_booking, or checkout_room_booking. The description only lists editable fields without usage context.

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