GET /room/bookings (Conexa Coworking > Booking)

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, making safety clear. The description adds behavioral context: items defined as array accept comma-separated values, and the attention notice about pagination behavior. No contradictions. The description supplements annotations well.

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: two core sentences plus a warning label. Every sentence adds necessary information. The purpose is front-loaded, making it efficient for an agent to parse. No extraneous content.

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?

Given the high schema coverage and annotations providing safety, the description is largely complete. It covers pagination, array parameter usage, and deprecation warning. No output schema exists, but for a listing tool, the description provides sufficient operational context. Minor gap: no description of return structure, but not critical.

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 the baseline is 3. The description adds minimal extra meaning beyond schema descriptions: it repeats that array parameters accept comma-separated values and stresses the limit requirement for new pagination. This is marginal value, hence score 3.

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 'Listagem paginada de Reservas de Sala' (Paginated listing of Room Reservations), specifying the verb 'list', the resource 'room bookings', and indicating pagination. It distinguishes from siblings like get_room_booking (single) and cancel_room_booking. The purpose is unambiguous.

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?

The description provides usage guidance on pagination, explicitly stating that the 'limit' parameter is mandatory for the new pagination model and warns about the deprecation of the old model. It does not explicitly differentiate from other list tools, but the resource specificity and pagination context are clear.

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