ctr_opportunities

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

No annotations are provided, so the description must disclose behavioral traits. It explains the metric calculation and warns against speculation, but it does not mention that the tool is read-only, any rate limits, or what happens with insufficient data. It also does not describe the output format or any side effects.

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 concise, consisting of three sentences. The first sentence states the purpose, the second defines the metric, and the third provides an important usage guideline. It is front-loaded and each sentence adds value, though the warning is slightly longer.

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?

Given 4 parameters and no output schema or annotations, the description should provide a more complete picture. It defines the core metric but fails to describe parameter roles, output structure, or thresholds for 'significantly below'. The tool's complexity is moderate, and the description leaves gaps.

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?

The schema coverage is 0%, meaning the description must compensate for missing parameter documentation. However, the description does not explain any of the four parameters (site_url, days, min_impressions, top_n). It only implies 'site_url' and 'date_range' in the note, but without explicit mapping to parameters. This is a significant omission.

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: listing pages with CTR significantly below expected for their position, and defines the CTR gap metric. It is specific and distinguishes from siblings like search_analytics, though no explicit verb like 'list' or 'retrieve' is used.

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 includes a strong 'IMPORTANT' note instructing the agent to use only the returned data and to cite site_url and date_range. This provides some guidance, but it does not specify when to use this tool versus alternatives such as 'search_analytics' or 'quick_wins', nor does it mention exclusions.

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