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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description does add behavioral value beyond that by disclosing the sort order and the criteria deliberately excluded from ranking, which tells the agent what the returned ordering means. It stops short of describing pagination or the shape of a recognition entry.

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 no filler, so it is not padded. However, the front-loaded clause 'Public recognition ordered by...' is cryptic enough that the reader must reconstruct the intent from the title rather than getting an immediate statement of what is returned.

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 carries the burden of explaining the return value, yet it never says what a checker entry contains, whether results are paginated, or how the two ordering keys interact. For a ranked-list read tool the agent is left guessing at the response shape.

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 'after' offset cursor at 100% schema description coverage, so the schema already documents the parameter and the baseline is 3. The description adds no detail about cursor semantics, page size, or how to iterate, leaving nothing extra on top of 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?

The title supplies the verb ('Read checker recognition') but the description itself opens with the vague noun phrase 'Public recognition,' never explicitly stating that it returns a list of checkers ranked by accepted checks. The ordering rules ('accepted checks, then evidence-backed upheld challenges') and the exclusions ('no rank for claims filed or paid memberships') do help separate it from search_checks, but the resource being returned is left to inference.

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 siblings like search_checks, read_check, or get_challenges, and no prerequisites. The 'no rank for...' sentence is a scoping note about the ranking, not guidance on selecting this tool.

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