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

Annotations already declare readOnlyHint=true, non-destructive and closed-world, so safety is covered. The description adds the important scope constraint that only reviews from brokered customers are returned, which the agent could not derive from annotations. It does not mention pagination despite max_results.

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 short sentence with no filler, front-loading the resource. It is concise but perhaps too short for a 2-parameter tool with no documented schema.

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?

No output schema exists, so the description should at least say what a review contains or how results are ordered/limited. With 0% parameter coverage and no output schema, the definition leaves the agent under-informed about both inputs and returns.

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 0%, so the description must carry the parameter load, but it says nothing about provider_id or max_results, including the 1-200 cap on results. The agent gets no guidance on what provider_id refers to or how max_results affects the response.

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?

States a specific resource (published reviews of a provider) and clarifies scope (only from brokered customers). It does not explicitly distinguish itself from the sibling submit_review, which is the write counterpart, but the verb 'Bewertungen veröffentlicht' implies retrieval.

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 when-to-use guidance, no exclusions, and never mentions submit_review as the alternative for submitting a review. The agent must infer that this is the read-side of the review flow from the name alone.

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