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

With no annotations, the description carries the behavioral burden. It clearly indicates this is a read-only, public-profile lookup, lists the returned profile and review fields, and discloses 20-per-page pagination plus accepted user_id forms. It does not mention rate limits, errors, or authentication expectations, but the 'public profile' wording and 'Get' verb make the operation's safety reasonably evident.

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 dense but efficient: one long sentence carries the core behavior and field list, and a second short sentence clarifies the key input. Every included detail contributes to correct invocation, with no filler.

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 two-parameter, read-only tool with no output schema, this description is complete enough for an agent to select and call it correctly. It covers the profile fields, review fields, pagination behavior, and where user_id comes from, leaving no critical invocation detail unspecified.

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%, so both page and user_id are already documented in the input schema. The description's note that 'user_id is a review's author_id' echoes the schema's own wording and adds no substantial new semantic information.

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 opens with a specific verb and resource: 'Get a Trustpilot reviewer's public profile' and enumerates the exact profile and review fields returned. The phrase 'across all companies' helps distinguish this from the company-scoped sibling trustpilot_company_reviews.

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 intended use is clear: retrieve a reviewer's profile and all their written reviews, and the guidance that user_id is a review's author_id helps the caller find the input. However, there is no explicit comparison to alternatives or statement of when not to use this tool; the distinction from company-level Trustpilot review tools is only implied.

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