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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is covered. The description adds valuable context beyond that: it says the output ties each enricher to the collections that enable it by default, and that per-item results live under the `enrichment` field.

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 tight sentences with no filler, leading with the resource and its example types before the collection-default detail. The phrasing is a noun phrase rather than an explicit verb ('list'), which slightly softens the front-loaded intent, but nothing is wasted.

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 parameterless, non-destructive list tool with no output schema, the description covers what is returned (enrichers plus their default collections) and where downstream results appear (`enrichment`). There is no meaningful gap an agent would hit when calling it.

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 and the schema is an empty object at 100% coverage, so there is nothing for the description to disambiguate. The 0-parameter baseline of 4 applies.

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 names a specific resource (enrichers) and enumerates concrete examples (YouTube videos, Wikipedia, repo stats, downloads, company profiles, TL;DRs), so an agent knows exactly what this returns. It does not explicitly distinguish itself from sibling list tools like list_adapters or list_collections, which keeps it out of 5 territory.

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?

Usage is implied — an agent would call this to discover available enrichers and their default activation per collection — but there is no explicit 'use when' statement, no prerequisites, and no mention of alternatives such as list_collections when the real question is about collections.

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