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

Annotations already establish readOnly, idempotent, non-destructive, and closed-world, so the safety profile is fully covered. The description adds one useful non-obvious fact — that discovery of checks carries no payment/approval side effect — plus the shape of what is returned, though it says nothing about result size, versioning format, or stability of the catalog.

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?

Two short sentences with the return contents front-loaded and the payment caveat last. 'Versioned broad checks' is the weakest phrasing — 'broad' is undefined and costs the reader a beat — but nothing is padded or redundant.

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 zero-argument discovery tool with no output schema, the description should carry the return shape, and it partially does (schemas, limits, proofs). However, it never says what domain these checks verify (bounty artifacts? PRs?), how results are ordered or paged, or how the agent should apply a 'what each check proves' entry afterward.

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 there is nothing for the description to disambiguate; the baseline applies. The mention of 'versioned' is the only hint that versions may matter, but with no input surface this dimension is essentially complete.

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 verb 'Find' plus the resource 'verification checks' is specific, and the description enumerates what is retrievable (versioned schemas, limits, what each check proves). It stops short of naming or distinguishing the obvious siblings like run_verification_checks or validate_verification_plan, so an agent must infer that this is the catalog/lookup counterpart.

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 explicit statement of when to call this versus run_verification_checks, validate_verification_plan, or get_verification_run. The only boundary cue is the negative one ('Checks do not approve payment'), which constrains expectations but does not route the agent to the right tool.

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