Trustpilot Data

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only says 'Fetch', implying a read operation, but does not disclose async behavior, return format, rate limits, or any side effects. The mention of a 'documented endpoint' is a reference to external docs, not a behavioral trait.

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 under-specified sentence that restates the tool name without providing useful information. It is not concise in an effective way; it is merely terse. There is a typo ('/trustpopic') that detracts from professionalism and clarity.

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?

Given the tool has six parameters, a rich schema, an output schema, and many sibling tools, the description is highly incomplete. It does not help the agent select this tool over alternatives, explain when to use async modes, or indicate typical use cases. The output schema exists, so return values need not be described, but all other context is lacking.

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 the baseline is 3. The description adds no parameter-specific meaning beyond the schema; it only references the endpoint. The schema already documents all six parameters, including 'query', 'fields', 'enrichment', and 'execution_mode', so the description adds minimal value.

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 action ('Fetch') and resource ('Trustpilot business data'), but 'business data' is vague and does not specify what type of data (e.g., ratings, company profiles) or distinguish it from sibling tools like 'trustpilot_reviews' and 'tp_data'. The reference to a '/trustpilot endpoint' is unclear and contains a typo ('/trustpopic'), further reducing clarity.

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 does not mention any context, prerequisites, or exclusions. Sibling tools like 'tp_data', 'trustpilot_reviews', and 'businesses_get' exist, but the description provides no direction on which to choose.

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