Get Ctr Optimization Report

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

With no annotations provided, the description carries the burden of behavioral disclosure. 'Find' implies a read-only reporting operation rough but factual, but the description does not explicitly confirm no side effects, explain how thresholds are applied, or describe pagination or sorting behavior.

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, well-structured sentence that front-loads the core behavior and value proposition. There is no filler or redundant restatement of the tool name.

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?

The description gives a clear one-line purpose and an output schema exists, but it lacks guidance on when to use this versus overlapping siblings send comparison behavior with other reporting tools or parameter thresholds. It is minimally viable for understanding what the tool does, but not fully complete for confident tool selection.

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 67%, with start_date and end_date lacking descriptions. The tool description adds the conceptual link between 'high impressions but low CTR' and the max_ctr_pct/min_impressions parameters, but it does not clarify date formats, search_type meaning, or threshold interactions beyond what the schema already states.

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 identifies the tool's purpose: finding pages with high impressions but low CTR, framed as 'quick-win optimization candidates.' It uses a specific verb and resource, though it does not explicitly differentiate from overlapping siblings like identify_quick_wins.

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 phrase 'quick-win optimization candidates' implies an optimization workflow, giving some contextual usage guidance. However, it does not explicitly say when to prefer this tool over siblings such as identify_quick_wins or get_search_analytics, nor does it mention exclusions or prerequisites.

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