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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe read operation. The description adds genuinely useful content behavior beyond those hints: results are editorially ranked on a 0–5 scale and include partner disclosure, which signals the response may surface affiliate/partner relationships. No contradiction with annotations exists.

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?

A single ~20-word sentence that front-loads the core purpose ('Ranked providers in a category') and then packs four payload attributes (editorial score, one-line summary, entry price, partner disclosure) with zero filler. Every phrase earns its place.

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 simple read-only list tool with no output schema, the description does a decent job characterizing the returned items (score, summary, price, disclosure), and the category enum in the schema is self-documenting. However, the limit parameter's semantics are unexplained, ordering/pagination behavior is absent, and the absence of sibling-routing guidance leaves agents to guess when this tool is the right call.

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 only 50% (category documented as 'Category slug', limit undocumented). The description adds semantic meaning to category by explaining it selects the ranking group ('in a category'), but says nothing about the limit parameter, whose role as max-result-count is left to inference from min/max constraints. The description partially compensates for the coverage gap but not fully.

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 title 'List ranked providers' plus the description 'Ranked providers in a category with editorial score...' states a specific verb (list) and resource (providers), and clarifies the output payload. It is implicitly distinguishable from siblings like get_provider (singular detail) and compare_providers (comparison), but it never names or explicitly contrasts them, so sibling differentiation is implied rather than stated.

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 gives no guidance on when to use this tool versus its siblings. It does not mention that compare_providers is the choice for side-by-side comparison, get_provider for a single provider's details, or search for cross-category discovery. The category-filtered context is implied by the schema but no when-to-use or when-not-to-use guidance is provided.

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