List Bookings

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

The description adds only that it lists the user's own reservations, implying authentication. With annotations providing readOnlyHint, there is no contradiction, but no further behavioral context (e.g., pagination, rate limits) is given.

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 extremely concise (one sentence) and front-loaded, but it omits necessary detail for a tool with nine parameters, making it under-informative.

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 complexity (9 parameters, no output schema), the description is incomplete. It does not explain output format, filtering behavior, or how parameters like open and sortList work.

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 description coverage is 0%, and the description provides no explanation for any of the nine parameters. The meaning of fields like researchFilter, open, sortList remains unclear.

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 the verb 'List' and the resource 'authenticated user's reservations' from 'myReservations', distinguishing it from sibling tools like search_huts or confirm_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?

The description implies usage for listing the user's own bookings but provides no explicit guidance on when to use this tool versus alternatives such as search_hut_availability or auth_status.

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