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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds useful information about return content (ratings, text, dates). However, it lacks behavioral details such as pagination, ordering, error handling, or rate limits. No contradiction between description and annotations.

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 extremely concise, with a single purpose sentence and a compact arg list. Every word adds value, and the most important information is front-loaded.

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?

For a simple two-parameter tool with read-only annotations, the description covers purpose, parameters, and return fields adequately. It falls slightly short by not offering explicit sibling tool comparison, but this is a minor gap given the tool's simplicity.

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 0%, but the description fully compensates by explaining both parameters: 'company' accepts a name or URL slug with an example, and 'max_results' is described as max reviews with a default. This provides semantic meaning beyond the bare schema.

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 the verb and resource: 'Get Trustpilot reviews for a company.' It also mentions the return fields (ratings, review text, dates), which provides a complete purpose. The platform-specific name and description distinguish it from sibling tools like g2_reviews and yelp_reviews.

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 usage is implied through the platform name and description, but there is no explicit guidance on when to use this tool versus the sibling review tools. No exclusions or alternatives are mentioned, so the agent must infer that this is for Trustpilot reviews.

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