Trustpilot Reviews

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

With no annotations, the description must carry the full burden of behavioral disclosure. It only says 'fetch reviews' and mentions an endpoint, without revealing important behaviors like pagination, async defaults, rate limits, or read-only guarantees. This is insufficient for a tool with 8 parameters.

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 a single sentence that front-loads the action 'Fetch Trustpilot reviews' and adds a helpful reference to the endpoint. It is concise with no wasted words, though it sacrifices depth for brevity.

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?

The tool has 8 parameters, an output schema, and many sibling review tools, yet the description is extremely sparse. It fails to explain when to use this tool, how async/webhook behavior works, or what differentiates it from similar tools, leaving the agent under-informed for confident selection and invocation.

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%, and the schema provides detailed descriptions for all parameters (query, execution_mode, reviews_limit, etc.). The description itself adds no parameter-level meaning, but the baseline of 3 applies when the schema handles parameter documentation well.

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 clearly states 'Fetch Trustpilot reviews' with a specific verb and resource, and references the documented endpoint. It tells the agent exactly what the tool does, though it doesn't explicitly distinguish it from sibling tools like tp_reviews or trustpilot_data.

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 gives no guidance on when to use this tool versus alternatives like yelp_reviews or tripadvisor_reviews. There are no exclusions, conditions, or alternative recommendations, leaving the agent without selection context.

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