POST /room/booking (Conexa Coworking > Booking)

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, but the description adds no extra behavioral context such as auth requirements, rate limits, or side effects. It merely lists input fields, which is already covered by 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?

The description is a long list of fields. While structured, it is verbose and could be more succinct. Each sentence earns its place, but the overall length detracts from readability.

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 covers all input fields thoroughly but lacks mention of the return value or output behavior. Given no output schema, an agent would benefit from knowing what the response contains. For a creation tool, this is a moderate gap.

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?

The input schema only defines a generic 'body' property, but the description fully enumerates all fields (customerId, personId, roomId, etc.) with formats and notes. This compensates for the minimal schema, providing meaningful semantics beyond the schema itself.

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 'Cadastro de uma Reserva de Sala de Reunião' (Registration of a meeting room reservation), which is a specific verb and resource. It distinguishes from siblings like cancel_room_booking, update_room_booking, and get_room_booking by focusing on creation.

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 such as update_room_booking or cancel_room_booking. The description does not mention prerequisites or context for using this creation endpoint.

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