List bookings

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the description focuses on ordering behavior (newest-first vs soonest-first for upcoming:true) and filtering, adding value beyond the annotations.

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?

Single sentence that conveys purpose, ordering, and filter options efficiently. Could be slightly restructured for readability, but no unnecessary words.

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 tool's simplicity (list with filters) and no output schema, the description covers the main aspects: resource, ordering, and filters. Could mention return type (list of bookings) 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 has 0% description coverage, so the description must compensate. It explains the status enum values, the effect of upcoming:true, and implies project is required. However, the company and project parameters are not fully described (e.g., project identifies the board).

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 uses specific verb 'List' and resource 'bookings', clarifies ordering 'newest-first', and differentiates from sibling tools like cancel_booking and other list_* tools by focusing on booking-specific filters.

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?

Clearly states filtering options by company, status, or upcoming flag. Provides context for ordering based on filter. Lacks explicit exclusion or alternative tools, but the use case is straightforward for a list endpoint.

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