Google reviews

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

Despite annotations only providing readOnlyHint=true, the description discloses significant behavioral traits: caching with a 5-minute TTL shared with the ratings tool, client-side filter application, a ~10 day Google data lag warning, pagination signaling via hasMore, and structured error codes with retryable flags. These enrich the agent's understanding of side effects, latency, and error semantics far beyond the annotation baseline.

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 extensively detailed yet efficiently structured with clear sections for purpose, pagination, filtering, caching, data lag, and error handling. Every sentence adds value, no filler content exists, and the most important purpose statement is front-loaded. Despite its length, it remains highly scannable and appropriately sized for the tool's complexity.

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 complexity (10 parameters, output schema, caching, rate limits, data lag), the description covers all critical operational aspects: differentiating use, pagination mechanics, filtering semantics, cache behavior, data freshness warnings, and error handling. The existence of an output schema means it doesn't need to detail return fields, and nothing essential is missing for an agent to correctly invoke and interpret this tool.

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?

Although schema description coverage is 100%, the description adds meaning beyond the schema. It explains pagination semantics ('Check hasMore in response'), clarifies that filters are applied client-side on cached data, and details the forceRefresh behavior and error code structure. This contextual information is absent from the raw schema properties and helps the agent use the parameters correctly.

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 opens with a specific verb and resource: 'Fetch individual Google reviews with pagination and filtering for sentiment analysis.' It clearly distinguishes itself from the sibling tool 'pinmeto_get_google_ratings' by directing users there for aggregate statistics. This unambiguous purpose, combined with explicit sibling differentiation, warrants a top score.

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 states when to use this tool versus an alternative: 'For aggregate statistics (averageRating, totalReviews), use pinmeto_get_google_ratings instead.' It also provides detailed guidance on pagination, filtering, caching, and error handling, giving the agent clear decision rules. This goes beyond basic context to include exclusions and alternatives.

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