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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description goes beyond by clarifying that the tool only measures disclosed-metadata completeness and is not a safety verdict or installation approval. This additional context sets correct expectations about the tool's limitations and behavioral traits.

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?

The description is extremely concise, using two sentences to convey purpose, scope, limitations, and disclaimers. Every sentence adds value, and the key action is front-loaded. No unnecessary words or repetition.

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 tool with low complexity (2 parameters, clear output schema), the description covers all essential aspects: what it does, what it measures, what it does not measure, and the number of entries. No gaps remain for an agent to misunderstand the tool's purpose or capability.

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 description coverage is 50% (only 'entries' parameter has a description). The tool's description reinforces the 'entries' parameter's role ('2-5 HeyClaude entries'), but adds no detail about the 'platform' parameter. Since coverage is borderline and the description does not fully compensate, a score of 3 is appropriate.

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 explicitly states the tool compares 2-5 HeyClaude entries by trust metadata coverage and ranks them by deterministic signal coverage. It uses specific verbs ('compare', 'rank') and identifies the resource ('entries'). This clearly distinguishes it from sibling tools like entry.trust or entry.safety.

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 description defines the tool's purpose clearly and explicitly states what it is not (malware scan, safety verdict, installation approval), which helps an agent avoid misuse. However, it does not explicitly contrast with sibling tools or provide direct 'when to use/not use' guidance, lowering it slightly from a 5.

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