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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and closed-world, so safety is covered. The description adds nothing beyond that: it does not say what a catalogue entry contains, whether results are paginated or complete, or what 'proof surfaces' means. With no output schema, this is a real gap.

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 short sentence with the verb and resource front-loaded and zero filler. It is efficient, though its brevity shades into under-specification rather than tight concision.

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 listing tool with no output schema and a free-form query object, the description should at least explain what is returned and how to filter. Neither is covered, leaving the agent unable to predict results or construct a useful query.

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?

One optional parameter whose schema description is only the generic 'Optional query parameters', with additionalProperties allowing any string/number/boolean key. Nominal coverage is 100% but content-free, and the description offers no filter keys, formats, or examples, so an agent has no way to know what to pass.

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 ('List') and resource ('Drive Pass checks and proof surfaces'), but 'proof surfaces' is undefined jargon that an agent cannot resolve from the text. The sibling drive_pass_check implies a catalogue/check split, yet the description never names or contrasts with it, so differentiation is left to naming convention.

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 statement, no condition, and no mention of the obvious alternative drive_pass_check (run a check) or right_pass_catalogue. The agent must infer from the name pattern that a catalogue lists rather than executes.

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