find_high_impression_low_ctr_pages

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

With no annotations provided, the description carries the full burden of disclosing behavior. It only says 'Find', implying a read-only query, but doesn't state that it returns a list of pages, respect pagination limits, or interact with GSC's sampling/rate limits. No side effects or constraints are mentioned, leaving the agent without a clear picture of what happens when the tool is invoked.

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 a single sentence, which is concise, but it is under-specified for a tool with 6 parameters, no annotations, and no output schema. It lacks the necessary context to be immediately actionable. While it has no fluff, its brevity does not serve the agent's need for guidance.

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 no annotations, no output schema, and incomplete parameter documentation, the description is far too thin. It does not explain return format, default thresholds, or how results are ordered, nor does it distinguish this from overlapping siblings. The agent cannot confidently invoke this tool correctly without additional probing.

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 50%, covering date and siteUrl, but not maxCtr, minImpressions, or rowLimit. The description says 'high impressions and low CTR' which vaguely maps to minImpressions and maxCtr, but doesn't explicitly tie these parameters to their roles or explain defaults. The tool name hints, but the description adds little semantic value beyond the schema.

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 a specific action ('Find') on a specific resource ('GSC pages') with clear criteria ('high impressions and low CTR'). It is distinct from siblings like gsc_top_pages, which list pages generally, and find_pages_with_clicks_but_low_engagement, which targets a different metric. However, it doesn't explicitly name alternatives, so it doesn't fully differentiate from all siblings.

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 gives no guidance on when to use this tool versus alternatives like seo_opportunity_report or gsc_search_analytics. It doesn't mention prerequisites, typical scenarios, or when a different tool would be more appropriate. The agent is left to infer usage from the tool name and schema.

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