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

Annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds behavioral context by specifying the output format (Markdown) and its contents (pricing, spec sheet, disclosure), which goes beyond the annotations. It does not cover error behavior or authentication, but that is not required given the safety hints.

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, dense sentence that leads with the core action ('Full review of one provider as Markdown') and enumerates content sections. No filler, and every word contributes to understanding the tool's output.

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 adequately conveys the return format and content. It does not explain how to obtain the slug (though the schema references list_providers) or clarify the category's role, but for a two-parameter read-only tool, the information provided is largely sufficient.

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 coverage is only 50% (slug has a description, category does not). The description does not mention parameters at all, failing to compensate for the missing schema description for category. The agent must rely on the enum alone, which lacks semantic context (e.g., what each category means or how it interacts with slug).

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 clearly states the tool retrieves a full review of a single provider, formatted as Markdown, with explicit sections (verdict, pros/cons, pricing, spec sheet, disclosure). This distinguishes it from siblings like compare_providers (multiple providers) and list_providers (listing providers).

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 implies usage for one provider but does not explicitly mention when not to use it or name alternatives. While the sibling list suggests compare_providers for comparisons, no direct guidance is given in the description, leaving the agent to infer the appropriate context.

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