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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds only the scope note (single keyword near a coordinate) and no return volume, rate-limit, or cost behavior; with an output schema present it does not need to explain returns, so this is adequate but thin.

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?

Two sentences, zero waste, with the resource and scope front-loaded before the usage caveat. No filler or repetition of the title.

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?

With a full schema and annotations covering safety, the description only needs to route the agent, which it does. Minor gap: it does not mention the depth cap or default language behavior, though both are documented in the schema.

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%, so the schema already documents keyword, near/latitude/longitude/radiusKm, depth, projectId, and languageCode. The description only restates that a keyword and coordinate are involved, adding no format or constraint detail beyond the schema baseline.

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 (fetches) and resource (Google Business Profile questions and answers), plus the scoping qualifiers ('one business keyword near a coordinate'). This clearly separates it from siblings like get_local_serp_results or search_local_businesses, which return different evidence.

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 sentence 'Run this only when Q&A evidence is needed' gives a gating condition but no named alternative and no exclusions relative to siblings. The agent knows the tool is Q&A-specific but is not told what to use instead when it wants reviews, categories, or local results.

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