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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that: no return shape, no pagination, no size/rate behaviour for a listing endpoint.

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 short, front-loaded sentence with no filler. It is efficient, though the brevity here reflects under-specification rather than disciplined editing.

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?

No output schema exists, so the description must explain what the catalogue returns and how it pairs with clearance_check; it does neither. For a catalogue/list tool in a dense family of 70+ siblings, this is not enough for an agent to call it confidently.

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 reported at 100%, so per the baseline the schema carries the parameter documentation and a 3 is appropriate. However, the single query parameter is an unconstrained additionalProperties bag with no named keys, and the description does not hint at any accepted filter keys, so the practical guidance is thin.

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 names a resource (Clearance Pass) and a verb (List), so the general purpose is inferable, but "checks and guidance" is vague about what is actually catalogued and does not distinguish it from the sibling clearance_check or the parallel *_catalogue tools (drive_pass_catalogue, right_pass_catalogue). An agent cannot tell from this text whether it returns check definitions, guidance documents, or both.

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?

There is no when-to-use guidance at all. The most obvious question an agent faces — catalogue vs. clearance_check, and how the two compose — is left entirely unaddressed, as is whether any query keys are expected.

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