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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful provenance context - the data is editorial curation, not measured performance - which helps an agent calibrate trust. It says nothing about pagination, locale behavior, or result size, so it stays at an adequate 3.

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, and the core purpose is front-loaded before the caveat. It is well-sized for the tool's simplicity, though the second sentence is doing double duty as both a scope statement and the only guidance offered.

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 no output schema, three fully undocumented parameters, and no annotation-level detail on return shape, the description leaves the agent without filter semantics or result expectations. The provenance caveat is valuable but does not fill the parameter and output gaps.

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% across three parameters (limit, locale, champion), and the description adds no meaning for any of them - it does not explain what 'champion' filters on, how 'locale' affects results, or how 'limit' interacts with editorial ordering. With such a low coverage rate the description was expected to compensate and does not.

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 (curated public combos) and a specific ordering principle (editorial tier), and it clarifies what 'top' does NOT mean by ruling out measured win rates and vote rankings. That contrast implicitly separates it from data-driven siblings like get_tier_list, though no sibling is named explicitly.

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 line 'These are suggestions, not measured win rates or vote rankings' implies when to reach for this tool (qualitative editorial picks rather than statistical rankings), but there is no explicit when-to-use statement, no prerequisites, and no named alternative. Usage must be inferred from the caveat.

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