Trustpilot Data

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 behavior. It does not mention that the tool may execute asynchronously (despite execution_mode and webhook params), rate limits, data scoping limitations, or any side effects. 'Fetch' implies a read operation but does not address the async complexity present in the schema.

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 concise sentence with no filler, and the core action and target are front-loaded. However, it is arguably under-specified for the tool's complexity, but the dimension rewards efficiency over completeness; there is zero waste.

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's 6 parameters, no annotations, several ambiguous sibling tools, and no usage guidance, the description is insufficient. The output schema exists so return values need not be described, but the description still lacks information about when to use it, what data is fetched, and how it relates to similar Trustpilot tools.

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 description coverage is 100%, and the description adds no extra parameter meaning. It does not clarify how 'enrichment' works, what 'fields' are valid, or how 'query' should be formatted beyond the schema. Baseline 3 applies because the schema already handles parameter documentation.

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 a specific verb ('Fetch') and resource ('Trustpilot business data'), so an agent knows what action is performed. However, it does not differentiate this tool from near-siblings like 'tp_data', 'trustpilot_reviews', or 'tp_reviews', and 'business data' is broad enough to overlap with other Trustpilot tools.

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, no exclusion criteria, and no mention of recommended use cases. It merely states what it does, leaving the agent to infer selection from the name and broad 'business data' phrase.

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