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

With no annotations, the description must carry the behavioral burden itself; it does disclose that this is a paginated, JSON-returning fetch for finished jobs. It does not address error behavior for unfinished jobs, authentication, rate limits, or idempotency, leaving part of the safety profile implicit.

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?

A single, tightly worded sentence front-loads what is fetched, how it is returned, and when it is valid. There is no filler or 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?

It provides the essential call-time facts (finished job prerequisite, JSON rows, pagination) and the schema handles parameters, but with no output schema or annotations it leaves row shape and failure behavior undocumented. For a simple paginated fetch this is adequate but not fully self-sufficient.

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 already documents all three parameters with 100% coverage, so the baseline is 3 and the description doesn't need to repeat them. The word 'paginated' aligns with limit/cursor but adds no new per-parameter meaning; cursor semantics are already in the schema ('from previous nextCursor').

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 names a specific action ('Fetch'), resource ('review rows'), output format ('as JSON'), and a lifecycle condition ('finished reviews job'), which clearly separates it from siblings like gmaps_get_reviews_job (job status) and gmaps_get_photos_results (photo rows).

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?

It states the operative context: this tool is for retrieving results only after the reviews job has finished, which is the main gate for using it. It doesn't explicitly name alternatives for checking job status or fetching non-review results, so it stops short of full when/when-not guidance.

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