List My Tickets

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

Beyond readOnlyHint and openWorldHint, the description discloses account-scoped results and newest-first ordering, while "logged-in account" also implies an authentication prerequisite. It adds no detail about pagination behavior, empty results, or authentication failures, so the additional behavioral context is useful but limited.

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?

One compact sentence front-loads the operation and account scope, then adds the useful ordering guarantee. There is no filler or redundant wording.

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?

For a read-only tool with no required parameters and an output schema, the account scope, ordering, and schema-defined filters are nearly sufficient for correct selection and invocation. Explicit single-ticket alternatives and a brief explanation of limit/offset pagination would address the main remaining 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 description provides no parameter-specific guidance; lang, states, and currency are documented in the schema, while limit and offset rely on their intuitive names, defaults, and bounds. With 60% schema coverage and simple optional parameters, this is adequate but does not compensate for the undocumented pagination fields.

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 verb "List," the resources "tickets and reservations," the logged-in account scope, and the newest-first ordering make the operation clear. It does not explicitly distinguish this collection listing from get_my_ticket or get_ticket for retrieving a single ticket or its details.

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 wording implies use when retrieving the current user's tickets and reservations rather than searching routes, locations, or other catalog data. There is no explicit when-not guidance or direction to get_my_ticket/get_ticket when the agent already has a ticket identifier or needs full details.

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