gmb_v4_accounts_locations_reviews_get

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, covering the safety profile. The description adds the resource hierarchy pattern, which clarifies the scope of the operation. It does not contradict annotations, but also does not disclose additional behavioral traits like permissions or error conditions.

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 one sentence, front-loaded with the HTTP method and resource pattern. Every word earns its place, and there is no fluff or repetition of schema details. It is appropriately sized for a simple GET operation.

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 simple read-only tool with rich annotations and a single parameter, the description is adequate for an agent to select and invoke it correctly. It lacks details on return format or error handling, but the lack of an output schema and the simplicity of the operation make this acceptable. The annotation hints (readOnly, idempotent) compensate for missing context.

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 one parameter 'name' with no description (0% coverage), but the description explicitly shows the expected path format 'accounts/*/locations/*/reviews/*'. This gives the agent the essential syntactic constraint. It does not elaborate on what the name represents, but the pattern is the core semantic.

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 clearly states the operation as 'Gets a review' with the full resource pattern 'accounts/*/locations/*/reviews/*'. This distinguishes it from sibling tools like 'reviews_list' (which lists reviews) and 'reviews_updatereply' (which updates a reply). The verb+resource structure is explicit and unambiguous.

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 usage: call this tool when you need to fetch a single review by its resource name. However, it provides no explicit guidance on when to prefer this over the sibling 'reviews_list' or other review-related tools. There are no explicit exclusions or alternatives mentioned.

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