google_maps_reviews: GET /

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

Annotations are not provided, so the description must carry the full burden of behavioral disclosure. It mentions 'Paginated fetch', which implies pagination behavior, and lists the exact fields returned (author name, profile link, star rating, etc.). This is valuable transparency. However, it omits details such as rate limits, error handling, the requirement to supply either dataId or placeId (which is only in the schema), and behavior when no results are found. With no annotations, a 3 is fair—it provides some behavioral context but leaves gaps.

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 concise and well-structured. It opens with a one-sentence summary, then a second sentence detailing the fetch parameters and returned data, and a final sentence on use cases. Every sentence adds value, with no redundancy or fluff. The key capabilities are front-loaded, making it easy for an agent to quickly grasp the tool's functionality.

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 that there is no output schema, the description compensates by listing the exact fields returned per review, which is highly useful for an agent. It also covers the input parameters and use cases. However, it does not explicitly state the requirement to set either dataId or placeId, and pagination behavior is only implied by the word 'paginated' without explaining the nextPageToken. These gaps prevent a perfect score, but overall, the description is quite complete for a fetch 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?

The schema has 100% coverage, with all six parameters having descriptions. The description adds minimal new meaning beyond the schema: it summarizes that sorting and filtering are possible and mentions language, but these are already in the schema. The description does not clarify parameter constraints further, such as the exact format of dataId or how nextPageToken is used. Since the schema already handles the semantics, a baseline of 3 is appropriate.

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 'Get Map Reviews' and then provides a detailed explanation: 'Paginated fetch of Google Maps reviews for a place by dataId or placeId, with sort...'. This clearly states the verb (fetch), the resource (Google Maps reviews), and the key distinguishing capabilities (pagination, sorting, filtering). It differentiates from sibling tools that handle photos, place details, posts, or search, leaving no ambiguity about the tool's purpose.

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 includes explicit use cases: 'Use for reputation management, sentiment and topic mining, competitor review benchmarking, and feeding review data into summarization or trust-score LLMs.' This provides clear context on when to use the tool. However, it does not explicitly state when not to use it or name alternative tools, relying on the sibling list for that. Since the context is clear but exclusions are absent, a score of 4 is appropriate.

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