Trustpilot Reviews (Legacy Alias)

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

No annotations are provided, so the description carries full behavioral burden. However, it only states that this is a legacy alias and does not disclose any actual behavior, side effects, or limitations. The agent learns nothing about what the tool does beyond its alias status.

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 two short sentences, front-loaded with the core alias information and a clear preference directive. No wasted words; every part earns its place.

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?

As a legacy alias, the key contextual information is that it should be avoided in favor of trustpilot_reviews. The description conveys this effectively. An output schema exists, so return values are documented. However, the description does not explain the tool's functionality, relying on the canonical tool's documentation, which is a minor gap.

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 information, but the schema already provides full descriptions for all 8 parameters, including 'execution_mode' and 'skip'.

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 this is a legacy alias for trustpilot_reviews, which is a specific resource and distinguishes it from sibling tools. The title 'Trustpilot Reviews (Legacy Alias)' reinforces this, making the purpose unambiguous.

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 explicitly instructs to 'Prefer trustpilot_reviews for new integrations', providing direct when-to-use versus when-not-to-use guidance. This is a clear recommendation of the alternative.

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