Trustpilot Reviews

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

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. The single sentence mentions the endpoint but reveals nothing about execution modes (async/sync), rate limits, error behavior, pagination, or side effects. Even the existence of an execution_mode parameter is not hinted at. This is insufficient for an agent to understand how the tool behaves beyond 'fetching.'

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 one short sentence, which is concise but severely under-specified. It does not front-load any critical scoping info or behaviors. The phrase 'with the documented /trustpilot-reviews endpoint' is filler that adds no value. For a tool with eight parameters and an output schema, this is too brief to be useful; it reads like a stub rather than a considered description.

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?

Despite having an output schema and eight parameters (including execution_mode and async), the description explains none of the operational context. It does not mention how to choose between sync/async, what fields can be requested, how pagination works, or what the response structure is. An agent would need to rely entirely on the schema and output schema, which may not capture runtime behavior. The description is critically incomplete for a tool of this complexity.

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 description coverage is 100%, so all eight parameters have descriptive text in the schema. The description adds no extra meaning to the parameters, but the schema already documents their roles. Per the rubric, with high schema coverage the baseline is 3, and the description does not lower that score. However, it also does not add any semantic clarity beyond the schema.

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 clear verb and resource ('Fetch Trustpilot reviews'), and mentions a specific endpoint. However, it does not differentiate this tool from several siblings with overlapping purposes (trustpilot_data, tp_reviews, tp_data), and the word 'documented' adds no distinguishing information. Without specifying scope or uniqueness, the purpose is clear but not well differentiated.

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 provides no guidance on when to use this tool versus alternatives. It neither states when to prefer it nor mentions any exclusions or prerequisites. There are many sibling review tools (e.g., yelp_reviews, tripadvisor_reviews) that could overlap, and the agent is left with no decision support. This is a complete absence of usage guidance.

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