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

Annotations already cover the safety profile (readOnly, not destructive, openWorld). The description adds useful context beyond them: the sort order ('soonest visit first'), the account scoping, and an authentication requirement ('Needs the user's Cotlet API key with access to this app'). Pagination and result limits are not disclosed.

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 compact sentences that front-load the action and scope before the downstream-tool guidance. The 'Tiqets:' prefix mildly duplicates the title but wastes little space.

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?

With no output schema, the description helpfully names the fields returned and the auth prerequisite, and there is only one optional parameter. The main gap is the absence of any mention of pagination or caps on the listing, but for a simple filtered-list tool it is largely 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 coverage is 100% and the single 'when' enum is fully documented in the schema, so the schema does the heavy lifting. The description adds nothing about the when/upcoming/past/all filter, so the baseline 3 is appropriate.

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?

States a specific verb and resource plus scope: 'Lists the bookings of the signed-in account, soonest visit first.' It also enumerates the returned fields (product, visit date, tickets, status) and differentiates from get_booking by pointing to where order_id should be reused, so an agent can distinguish it from siblings.

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 names the downstream tools (get_booking, download_tickets, cancel_booking) and the value they consume, giving clear workflow context. It lacks an explicit 'use this instead of get_booking when you want the full list' statement, so usage is implied rather than spelled out.

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