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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the useful behavioral note that results come one Google-paginated page at a time, but does not explain authentication needs, rate limits, or pagination-token behavior beyond that single phrase.

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 sentence, front-loaded with scope and resource, with no wasted words. The pagination constraint is included compactly, and nothing extraneous is present.

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 read-only, two-parameter listing tool with rich annotations and no output schema, the description covers resource, scope, safety, and pagination behavior. The remaining gap is pageToken mechanics, but the annotations and pagination phrase provide enough context for a basic call sequence.

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 50%: projectId is documented in the schema, while pageToken is not. The description's 'one Google-paginated page at a time' signals that pagination exists but does not explain how pageToken should be used, so it only partially compensates 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 identifies a specific resource ('reviews') scoped to the project's linked Google Business Profile location, clearly distinguishing it from sibling tools about posts, profile, performance, or questions. It does not name an alternative tool, but an agent can identify the core purpose from the resource and scope.

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 implies when to use it: to read reviews for the project's linked GBP location, one page at a time. It provides no explicit when-not guidance and does not name alternatives such as list_gbp_posts or get_gbp_profile, leaving usage context implied rather than directed.

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