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

Annotations already declare readOnly, idempotent, and non-destructive, so safety is covered. The description adds real behavioral value beyond them: the source is a signed revocation list, and it disambiguates that 'unknown' means unvetted rather than unsafe — a distinction that changes how an agent acts on the result.

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 pre-install purpose and result categories are front-loaded in one dense sentence, followed by a compact call example. No filler; every clause either scopes the check or disambiguates an outcome.

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 an output schema present and annotations covering the safety profile, the description need not explain return values — yet it usefully sketches the outcome categories. The only meaningful gap is the missing guidance on how the three alternative identifier inputs relate to one another.

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 0%, so the description must carry the load, and it does: it clarifies that the hash is SHA-256, the url may be an endpoint or package URL, and the slug is a store slug, plus a concrete invocation example. It omits whether exactly one of the three optional inputs is required and how conflicts between them are resolved.

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 and resource ('pre-install check against the Rightshold Store and its signed revocation list') and enumerates the exact answer space: on record, vetting tier, rating record, REVOKED, or unknown. An agent can distinguish this from siblings like search_store or registry_lookup without opening either 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 'pre-install' framing establishes clear when-to-use context, and the REVOKED/unknown interpretation tells the agent what to do with the result ('do not install'). It does not name an alternative tool or state exclusions, so it stops short of full routing guidance.

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