review-intelligence-mcp-server

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds that it returns ratings, pros, cons, and use cases, but does not disclose any additional behavioral aspects such as data freshness, rate limits, or potential errors. It does not contradict 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: two opening sentences followed by a brief Args block. It is front-loaded and contains no filler. Every sentence adds value.

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 tool with two parameters and no output schema, the description sufficiently conveys what is returned (ratings, pros, cons, use cases). However, it does not mention pagination, result ordering, or any filtering beyond 'max_results', which might be needed for completeness.

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 input schema has 0% description coverage, but the description compensates by explaining the 'product' parameter with an example and 'max_results' with its default and meaning. This adds value beyond the schema's bare type definitions.

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 tool name 'g2_reviews' combined with the description 'Get G2 software reviews' clearly states the action (get) and resource (G2 reviews). It distinguishes itself from sibling tools trustpilot_reviews and yelp_reviews by specifying the platform.

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 indicates that this tool is for retrieving G2 reviews. While it does not explicitly state when not to use it or provide alternatives, the context of sibling tools makes the usage domain clear. No further guidance is given, but it is adequate for a single-platform tool.

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

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds the return fields (ratings, review text, dates), which is useful but does not disclose additional behaviors like pagination or rate limits. The description does not contradict 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 (three short lines), front-loaded with the purpose, and every sentence provides essential information without redundancy.

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 simplicity (2 parameters, no nested objects), the description adequately covers purpose, parameter semantics, and return values. No output schema exists, but the return fields are listed. Minor omission: no mention of pagination or error handling, but this does not significantly hinder use.

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 explains the 'company' parameter as 'Company name or Trustpilot URL slug (e.g. 'amazon.com')' and 'max_results' as 'Max reviews (default 20)'. This adds meaningful context beyond the schema's type and default values.

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 'Get', the resource 'Trustpilot reviews', and specifies the return values (ratings, review text, dates). This distinguishes it from sibling tools like g2_reviews and yelp_reviews by naming the platform.

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?

No guidance is provided on when to use this tool versus alternatives (g2_reviews, yelp_reviews). There is no mention of prerequisites, exclusions, or contextual tipping points.

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

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

Annotations already declare readOnlyHint=true and openWorldHint=true. Description adds that it returns photos, which is a behavioral detail, but does not disclose rate limits, authentication needs, or potential errors. With annotations covering the safety profile, description adds marginal value.

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?

Description is concise: one sentence for purpose followed by an Args block. Front-loaded with purpose. No wasted words, though the Args block could be integrated more naturally. Still efficient.

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 tool with 3 parameters and no output schema, the description covers purpose and parameter usage fairly well. However, it lacks details about output format, error messages, or any prerequisites. While adequate for a simple read-only tool, it leaves some gaps.

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 includes an Args section that explains each parameter with examples (e.g., 'pizza' for business, 'Chicago' for location, default 20 for max_results). This adds meaning beyond the schema's type and default fields, helping the agent understand usage.

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?

Description clearly states 'Get Yelp business reviews' with specific verb and resource. Examples of returned data (ratings, review text, photos) further clarify purpose. Distinguishes from sibling tools g2_reviews and trustpilot_reviews by explicitly naming Yelp.

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?

No explicit guidance on when to use this tool versus siblings. Agent can infer from the name and description that it's for Yelp, but no when-not or alternatives mentioned. Adequate but not helpful for selection.

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