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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by enumerating the returned signal set (stars, last-push recency, gone/archived/deprecated flags, collision count, verdict enum) and the word 'live' implies freshness. It omits error behavior for unknown names and any caching/rate-limit notes.

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 dense sentence with the resource and the lookup key front-loaded, then the return payload. No filler, no repetition of the title.

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 describing return values and does so thoroughly, including the verdict enum. For a one-parameter read tool that is nearly sufficient; only the failure mode for a non-existent or ambiguous name is unaddressed.

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?

Schema coverage is 100% and the single parameter is documented, so baseline is 3; the description earns an extra point by supplying a concrete example name format ('io.github.owner/name') and stressing 'exact', which clarifies that partial or display names will not resolve.

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 ('Get the live health verdict') and resource ('one MCP server'), scoped by exact registry name. The distinction from fuzzy siblings like census_search is implicit in the word 'exact' plus the example name format, so an agent can identify the right tool without opening the schema.

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?

The phrase 'by its exact registry name (e.g. io.github.owner/name)' signals that this is a precise-key lookup rather than a fuzzy search, which is the key routing decision against census_search and census_lookalikes. It does not explicitly name those alternatives or state what to do when the exact name is unknown, so it stops short of a 5.

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