Find quick-win keywords (striking distance)

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

Annotations already establish readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is known. The description adds valuable behavioral details: it groups results by page and optionally maps to WordPress post IDs when a WordPress site is configured. This goes beyond the annotations and clarifies the output organization without contradicting them.

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 two sentences with no redundancy. It front-loads the core purpose and adds the WordPress mapping detail efficiently. Every phrase earns its place.

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 tool with 9 parameters and no output schema, the description provides the essential context: the target range, the quick-win concept, and the WordPress integration. Parameters like siteUrl and date formats are covered in the schema, and the tool's read-only nature is handled by annotations. The only minor gap is the lack of explanation about the output structure, but since there is no output schema and the use case is clear, it is sufficient.

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 only 44%, so the description should compensate. It does explain the default position range (8-20) and the overall intent, but it does not elaborate on parameters like top, minImpressions, or minPosition/maxPosition beyond their names. The names are self-explanatory, but the description could have clarified relationships (e.g., how minImpressions affects results). It adds some value but does not fully compensate for the coverage gap.

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 specific verb ('Find'), resource ('queries with high impressions but average position in a range'), and the qualifying condition ('pages already ranking on page 1-2 that can be pushed into the top results'). This clearly distinguishes it from siblings like gsc_ctr_opportunities (focused on CTR) and keyword_suggest (keyword generation). The purpose is 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 clearly conveys when to use this tool: when seeking quick wins by improving pages in positions 8-20. It gives concrete context (title/content/internal-link work) but does not explicitly name alternative tools or exclusion criteria. Still, the usage scenario is obvious and distinct enough from the listed siblings.

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