listBookings

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

No annotations provided, so description must fully convey behavior. It does not mention pagination, default limit, sorting, or what happens without filters. The read-only nature is implied but not stated. This is a significant gap for a listing tool.

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?

Three concise sentences that front-load purpose, followed by filtering capabilities and an example use. No waste.

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?

Missing output schema, no mention of response format, default sorting, or pagination limits. For a list tool with 6 parameters, the description should cover these to be complete.

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 descriptions cover 4 of 6 parameters, but the description adds no extra insight beyond the schema. The 'page' and 'limit' parameters lack descriptions, and the description does not explain pagination behavior. Schema description coverage at 67% is moderate, but the description fails to compensate.

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?

Description explicitly states 'retrieve confirmed, cancelled, or rescheduled meetings' and gives examples, making purpose clear. However, it does not strongly differentiate from sibling tools like getBooking (singular) or listParticipants.

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?

Provides explicit usage contexts: 'when you need to retrieve meetings', 'check a participant's upcoming meetings', 'find a specific booking before rescheduling or cancelling'. This guides when to use the tool, though it could mention when not to (e.g., for a single booking use getBooking).

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