gmb_verify_verificationtokens_generate

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

Annotations indicate readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the agent understands this is a non-read, non-idempotent mutation. The description adds minimal context beyond this: it says the token is used 'to verify the location'. It does not disclose side effects, token expiry, or that the caller must be an owner/manager (though that is in the schema). Since annotations already provide the safety profile, a score of 3 is appropriate for the small additional value.

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 concise, with only two sentences. The first provides the exact API endpoint, and the second states the core purpose. There is no redundant filler. The only slight deficiency is that the second sentence could be more precise (e.g., specifying 'instant verification token'), but it is still efficient and front-loaded.

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 description is overly minimal for a tool that participates in a multi-step verification workflow. It lacks information about what the token is used for, how it relates to sibling verification tools, and what the response looks like (no output schema). Given the complexity of the API and the presence of several verification-related siblings, the description does not provide enough context for an agent to use it correctly in a broader process.

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 100%, with detailed descriptions for all parameters (e.g., locationId, fields, quotaUser). The tool description adds no additional parameter semantics beyond what the schema already provides. The phrase 'provided location data' is vague and does not enhance understanding. Baseline 3 is applicable because the schema carries the full burden.

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 clear verb and resource: 'Generate a token for the provided location data to verify the location.' This distinguishes it from generic operations and gives a specific outcome. However, it does not explicitly differentiate from sibling tools like gmb_verify_locations_verifications_complete or gmb_verify_locations_fetchverificationoptions, which also relate to verification. The verb 'generate' and resource 'verification token' are specific enough to avoid ambiguity.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., locationId from an unverified listing) or the relationship to other verification steps. The sibling tools include several verification-related operations, and without any contextual cues, an agent cannot determine when to choose this over gmb_verify_locations_verify or gmb_verify_locations_verifications_complete.

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