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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety is covered. The description adds meaningful behavior beyond that: results are task-bound, can be verified via check_url in Incognito, and personalized factors like search history are ignored. It doesn't mention task expiry or freshness windows, but the core behavioral profile is communicated.

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?

The description is padded with marketing-style explanation about emulating parameters with highest accuracy and ignoring personalization. The first sentence states the purpose, but the remainder is verbose and tangential for a straightforward result-fetch endpoint. The pricing block is boilerplate rather than tool-specific guidance.

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?

Given one fully documented parameter, annotations covering safety and idempotency, and an output schema present, the description is broadly sufficient. The main gap is the absence of explicit linkage to the corresponding submit endpoint and task expiry behavior, which would help an agent chain calls correctly.

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%, and the schema fully documents the single 'id' parameter as a UUID task identifier with a 30-day retention window. The description adds no parameter-level detail beyond what the schema reliably provides, so the baseline of 3 is appropriate.

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 states a specific resource: reviews published on Trustpilot, specific to a business entity. This distinguishes it from sibling *_submit tools, which presumably create the task rather than fetch results. However, it doesn't explicitly name the paired *_submit alternative, so the differentiation is implicit 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?

There is no explicit statement of when to call this tool versus alternatives. The description implies result retrieval but never explains the submit-then-fetch flow or that the 'id' comes from a prior submit task. An agent must infer its usage from the surrounding tool set.

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