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

readOnlyHint=true already establishes this is a safe read, so the description only needs to add context. It does add a little — the catalogs are 'versioned' and there is defined 'unknown-evidence semantics' — but says nothing about output shape, catalog size, or how the two catalogs relate. Adequate but thin against the lower bar set by annotations.

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; the verb and resources come first. It is jargon-heavy ('unknown-evidence semantics'), which costs a little clarity but nothing is wasted.

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 parameters and no output schema, the description should ideally convey what an agent gets back (a list of check identifiers with grading rules, etc.). It names the content domains but never describes the return form, so an agent cannot predict the response structure.

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 tool takes zero parameters, so the baseline of 4 applies. There are no arguments whose semantics could be misunderstood.

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 gives a concrete verb (Read) and names the resources: a versioned 25-check linter catalog, a separate 14-check compliance catalog, plus grading rules and unknown-evidence semantics. That is more than a restatement of the name 'list_conformance_checks'. Sibling tools (scan, referral, trial, service) are unrelated, so no differentiation is needed, but the dense phrasing leaves it slightly ambiguous whether it returns the checks themselves or the catalog metadata.

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 alternatives, no prerequisites, and no exclusions. The siblings are in unrelated domains, so the omission is less costly, but the description offers no usage context at all.

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