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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe-read profile is covered. The description adds that results are related business profiles, but says nothing about how many, pagination, or whether the slug must come from trustpilot_business. With annotations carrying the safety burden, a 3 is appropriate.

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, no filler, with the primary action front-loaded followed immediately by the use case. Every sentence 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 one-parameter read-only tool with an output schema and annotations, the description covers purpose, trigger, and return content, which is close to sufficient. It lacks guidance on sourcing the required slug, which is the only real gap.

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 100% for the single slug parameter. The description adds the qualifier that the slug is a 'known Trustpilot business slug', which is marginally more meaningful than the schema's bare 'Resource slug', but it does not explain format or how to obtain a valid slug. Baseline 3 holds.

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 verb (list) and resource (businesses related to a Trustpilot business slug), and the word 'related' plus 'slug' distinguishes it from trustpilot_business and trustpilot_business_reviews. It stops short of explicitly naming the sibling it complements, so an agent must still infer the boundary rather than being told.

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?

"use this when comparing a business with similar companies" gives a clear when-to-use condition. There are no explicit exclusions or named alternatives (e.g., pointing to trustpilot_business to obtain the slug first), so it falls short of a 5.

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