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. The description adds only one piece of non-structured information: that the response contains the check schema, which is useful but minimal.

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, front-loaded with the verb, with no filler. It is efficient, though bordering on under-specified rather than genuinely concise.

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 must convey something about the return payload, and it does say the result includes checks and schema. However, it does not explain the shape of a check entry, how to feed a selected check into edge_audit, or what the loose 'query' filter accepts, which leaves real gaps for a catalogue/discovery tool.

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 schema has 100% description coverage and only a single optional 'query' object, so the schema carries the burden. The description says nothing about the query parameter, its accepted filter keys, or valid values, so it adds no meaning beyond 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?

States a specific verb (List) and resource (Edge Audit checks and schema), which matches the *_catalogue convention used by siblings like age_catalogue and ballot_catalogue. It does not explicitly distinguish itself from the paired action tool edge_audit, leaving the agent to infer that this one enumerates rather than evaluates.

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 statement of when to call this versus edge_audit, nor any prerequisite or ordering guidance. The agent must guess that the catalogue should be consulted before running a check.

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