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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is covered and the bar is lower. The description's only added signal is that the result is a listing of checks and their sources; it says nothing about pagination, auth, or how the query narrows results.

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?

A single, front-loaded sentence with no filler or repetition. It is efficient, though the brevity edges toward under-specification rather than true economy for a catalogue tool.

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?

Low-complexity read-only tool with no required parameters and no output schema, so the description need not explain return values. Still, it leaves the nested free-form query object unexplained and never defines what a 'check' or a 'source' is, which is the main knowledge an agent would need before calling it.

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 reported at 100% (the lone optional 'query' object carries its own description), so the baseline of 3 applies. The description contributes nothing about what keys the free-form query object accepts or how filtering behaves, so it adds no meaning over the schema.

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?

Clear verb + resource: 'List' plus the specific subject 'Ticket Pass checks and sources'. However, it never distinguishes this discovery/catalogue endpoint from the sibling execution tools ticket_check, ticket_scan, or ticket_issue_pass, and 'checks and sources' is loose vocabulary an agent must interpret.

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 when-to-use or when-not-to-use guidance. With ~80 sibling tools, many sharing the *_catalogue namespace (age_catalogue, finance_catalogue, travel_catalogue), the description provides no criteria for choosing this tool over ticket_check or a neighbouring catalogue.

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