CTR opportunities (page-1 rankings with weak CTR)

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

Annotations already provide readOnly, idempotent, and non-destructive hints. The description adds value by explaining the underlying logic (weighted by impressions) and providing concrete CTR benchmarks by position, which goes beyond the annotations and helps interpret results.

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 filler. It leads with the core function and immediately provides actionable benchmarks, making it efficient and scannable.

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 8 parameters and no output schema, the description should explain what the tool returns. It implies a list of queries/pages but does not detail output fields, sorting, or caveats like data lag (though the schema mentions lag). It is adequate for understanding the concept but incomplete for a fully self-sufficient call.

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 only 38%, so the description should compensate. It references 'top positions' (relating to maxPosition) and 'impressions' (relating to minImpressions) but does not explicitly define top, dimension, searchType, or other parameters. It adds some context but not enough to fully bridge the schema 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 clearly states the tool finds queries ranking in top positions with CTR far below the position benchmark, weighted by impressions, and explicitly names the use case (fastest wins from rewriting titles/meta descriptions). This distinguishes it from siblings like gsc_search_analytics or gsc_opportunities, which are broader.

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 when to use it (when seeking CTR improvements from titles/meta) but does not explicitly mention alternatives or conditions for choosing this over gsc_opportunities or gsc_search_analytics. The guidance is implicit rather than explicit.

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