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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful context — that personalization and search history are ignored and that results emulate the real search — but it omits the async task model (submit first, then fetch by id) and id expiry, which is only in the schema.

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?

It is front-loaded with the resource, but a large fraction of the text ('We emulate set parameters with the highest accuracy...', repeated relevance claims) is marketing boilerplate that does not help an agent invoke the tool and dilutes the signal.

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 an output schema present and annotations covering safety, the remaining burden is small; the id semantics are in the schema. However, the boilerplate describes the POST task rather than the fetch, so the async workflow the agent must understand is never made explicit.

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 sole id parameter is fully documented as a UUID with a 30-day validity window. The description adds nothing about the parameter, so the baseline of 3 applies — the schema carries the load.

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?

It states a specific resource — 'a list of business profiles listed on the Trustpilot platform' — but frames it around 'the keyword specified in a POST request,' which describes the prior submit task rather than this id-based fetch. It never explicitly distinguishes itself from trustpilot_search_submit or trustpilot_reviews_fetch, leaving the agent to infer the submit/fetch pairing.

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 when-to-use guidance: nothing says this retrieves the results of a previously submitted Trustpilot search task, nor when to prefer it over trustpilot_search_submit or the reviews siblings. The only actionable hint is the incidental mention of check_url for verification.

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