low_ctr_opportunities

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description earns credit for disclosing the analytical methodology (site median per position when data suffices, otherwise a benchmark curve, and how ratio is applied), which is real behavior beyond the annotations. It says nothing about how the 'enough data' threshold is decided or about row limits/pagination, leaving those gaps.

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 tight sentences, front-loaded with the core definition before the methodology. Every sentence carries information and nothing is padded. Only minor deduction for the methodology clause being formatted loosely rather than structured.

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?

An output schema exists, so return values need not be described, and annotations cover safety. But with 12 parameters at 0% schema coverage, the description is not complete enough for an agent to use the filtering knobs correctly. Adequate for the core concept, insufficient for invocation.

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 0% across 12 parameters, so the description carries the full burden, yet it only explains ratio ('0.5 flags rows under half the expected CTR'). It implicitly hints at max_position via 'page one' and at min_impressions via 'when there is enough data', but days, limit, source, search_type, start_date, end_date, max_rows and query_filter are entirely unexplained.

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+resource: query/page pairs on page one whose CTR underperforms their position, plus the diagnostic intent (title/snippet work). An agent can identify it as a CTR-anomaly detector. It does not explicitly distinguish itself from siblings like striking_distance or content_movers, which likely also surface underperformance, so it stops short of a 5.

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?

Usage is implied rather than stated: the closing phrase 'title/snippet work' signals the remediation context, and 'page one' scopes it to visible results. There is no explicit when-to-use-vs-alternatives guidance, no mention of excluding pages still in striking distance, and no prerequisite notes beyond the required site_url.

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