trustpilot_company_and_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. It discloses no behavioral traits such as rate limits, authentication needs, data freshness, pagination behavior, or output structure. The description only enumerates operations and their required parameters, leaving the agent uninformed about side effects or access constraints.

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 well-structured: a one-sentence summary followed by a clear list of operations with required params. Each line is informative, though the overall length is substantial due to the ten operations. It is concise relative to the complexity covered.

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 10 distinct operations, no output schema, and no annotations. The description provides operation names and required parameters but omits return formats, data types beyond string enums, error behavior, and operational caveats. It is minimally viable for selecting an operation but not fully complete for a multi-operation tool.

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?

The schema provides generic args and an operation enum, but the description adds essential meaning by mapping each operation to its required parameter (e.g., company_details requires company_domain, category_search requires query). This mapping is critical for invoking the tool correctly and goes beyond the schema's generic description.

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 explicitly states 'Trustpilot company search, company details, reviews, and category company listings' and then enumerates ten distinct operations, giving a clear and specific verb+resource for each. This clearly differentiates it from sibling tools like yelp_business_data or local_business_data, which target other data sources.

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 guidance on when to use this tool versus alternatives. The description lists operations and required parameters but does not discuss context, prerequisites, or exclusions. The agent is left to infer usage purely from the tool name and the raw operation list.

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