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

Annotations already establish the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar for additional disclosure is lower. The description earns credit by disclosing the shape of the read result in detail (criteria, ranking entries, 0-100 editorial score, best-for, key facts), which is genuinely useful since no output schema exists. It does not mention pagination, truncation, or behavior when a filter matches nothing.

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 sentences with no wasted words: the first front-loads what the tool returns, the second states the optional narrowing. Everything is load-bearing and easy to scan.

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 properly compensates by enumerating the return contents, and annotations cover the safety profile, making this largely complete for a two-parameter read tool. The remaining gap is guidance on obtaining the 'list' slug and on filter-miss behavior, neither of which is addressed.

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 100%, so both parameters are already documented in the schema, and the description's filter examples (free, open-source, linux) merely restate the schema's own enumeration. Baseline 3 is appropriate since the schema carries the semantics rather than the description.

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 gives a specific verb-and-resource ('One ranked list') and enumerates its payload (criteria, how to choose, every entry with rank, editorial score, verdict, best-for, key facts), which is far more concrete than a tautology. It does not name a sibling, so an agent must infer the boundary against list_rankings (which enumerates available lists) and get_product on its own.

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 only implied: an agent can deduce that it needs a list slug and that a filter is optional, but the description never states when to reach for this tool versus list_rankings, search_catalog, or get_product. It also omits that the slug must come from list_rankings/search_catalog, information that lives only in the schema.

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