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

Annotations already cover readOnly, idempotent and non-destructive, so much of the description's safety framing is redundant. However, it adds genuinely new behavior beyond the structured data: the enumerated response values and the fact that a verified listing returns no options, which prevents misinterpretation of an empty result.

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?

Three tight sentences with no waste; the core purpose and the read-only nature are front-loaded before the edge case. Enumerating all five verification methods is slightly verbose but earns its place by clarifying return values.

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?

The output schema removes any need to explain return format, and annotations cover the safety profile, so the description is close to complete. The remaining gaps are the undefined location parameter and the absence of explicit sibling routing, which leave the agent with inference to do.

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 coverage is 0% and the single required parameter "location" is completely undescribed in both schema and description. An agent cannot tell whether location expects a place ID, a name, or an address. With low coverage the description must compensate, and it does not.

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?

States a specific verb (Shows) plus the exact resource (which verification methods Google offers for a listing) and enumerates the returned values. The phrase "Starts nothing — read-only" implicitly distinguishes it from the sibling gbp_start_verification, so an agent can tell them apart.

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: the tool reads options, so it presumably precedes gbp_start_verification/gbp_complete_verification, but neither is named and no when/when-not condition is stated. The one edge case given ("An already-verified listing returns no options") adds some guidance but does not route the agent between alternatives.

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