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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered; the description's 'Read-only' is redundant. However, with no output schema, the description does carry real value by disclosing the shape of the result: who was contacted, when, whether text or email, which requests failed, and the count of Google reviews since the first send.

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 front-loaded sentence plus a two-word read-only marker; the parenthetical enumerates the returned fields efficiently. No filler, though the phrasing is slightly dense for what is essentially a status report.

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 two-parameter read-only tool with no output schema, the description gives enough to predict the response contents and the intent. The only material gap is the `days` window semantics, which is neither in the schema description nor the prose.

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?

Only the `client` parameter is documented in the schema (coverage 50%); `days` has no description, and the description does not clarify that the lookback window is bounded (default 90, max 365) or that 'since the first one' is evaluated inside that window. With a 50% coverage rate, the description does not fully compensate for the undocumented parameter.

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 states a specific resource (review requests sent to a client plus Google reviews received since the first request) with sub-details (who, when, channel, failures). It is clearly a read/status tool, distinguishable from the write-side siblings review_request_send and review_request_candidates, but it never names those siblings explicitly.

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?

Usage is only implied: 'Read-only' plus 'what went out' signals a retrospective status check rather than a send, which implicitly contrasts with review_request_send. There is no explicit statement of when to call this versus gbp_reviews (for the reviews themselves) or review_request_candidates, and no prerequisites mentioned.

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