trustpilot_business_reviews

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

No annotations provided. Description mentions parsing from public page, implying web scraping, but doesn't disclose rate limits, auth needs, or potential for site changes. Discloses date_from/date_to are 'currently rejected by upstream', a useful caveat.

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?

Two sentences, clear first sentence. Second sentence repeats 'Returns paginated Trustpilot business reviews' unnecessarily, causing slight redundancy.

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 9 parameters, no output schema, and no annotations, the description is minimal. Does not explain pagination details, return format, or any error handling. Schema descriptions are good, but overall completeness is adequate but not thorough.

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 baseline is 3. Description adds no additional meaning beyond the schema parameter descriptions (e.g., 'slug', 'stars', 'verified').

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?

Clearly states verb 'Get' and resource 'Trustpilot business reviews', with source 'parsed from the public review page'. Distinct from sibling tools like trustpilot_business and trustpilot_search.

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?

No guidance on when to use this tool versus alternatives (e.g., trustpilot_business for business info, trustpilot_business_search for finding businesses). Lacks 'when-not' or prerequisite information.

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