get-my-bookings

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

Without annotations, the description carries full burden. It describes a simple read-only list operation, which is transparent. However, it does not mention pagination behavior, ordering, or whether the operation is idempotent. A score of 3 is appropriate given the minimal but accurate disclosure.

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 single, concise sentence. It efficiently conveys the core function. However, it could be slightly improved by including the scope (e.g., 'your own bookings') without adding significant length.

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?

There is no output schema, and the description does not explain what fields a 'booking event' contains. For a simple list tool, this omission limits completeness. Additionally, no context is given on prerequisites or typical use cases. A score of 2 reflects these gaps.

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 covers both parameters (page, perPage) with descriptions, resulting in 100% coverage. The description 'List your booking events' adds no additional semantic meaning beyond the schema, so the baseline score of 3 applies.

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 'List your booking events' states a specific verb ('List') and resource ('your booking events'), making the purpose clear. However, it does not differentiate from sibling tools like 'book-event' or 'get-my-jobs', which could cause confusion.

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. There are sibling tools like 'book-event' for creating bookings and 'get-my-jobs' for jobs, but the description does not clarify that this tool is only for the authenticated user's bookings or when it should be preferred.

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