gsc_ctr_opportunities

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

With no annotations, the description carries the burden of behavioral disclosure. It does state that results are sorted by estimated clicks left, which is a useful behavioral trait. However, it doesn't explicitly state whether the tool is read-only (though implied), nor does it explain how parameters like date ranges affect behavior. The description adds some context beyond the schema but lacks depth on side effects or limitations.

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 well-structured with an opening concept paragraph followed by an args list. It front-loads the core value proposition and keeps parameter explanations brief. It's reasonably concise, though the prose could be trimmed slightly without losing meaning. The structure aids readability.

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 the output schema exists, the description doesn't need to explain return values, but it does need to explain how to use all parameters effectively. It covers the purpose and three key parameters, yet omits guidance on date range parameters and site_url, which are critical for scoping queries correctly. Defaults are provided, but an agent lacks context on when to override them. The description is adequate for a basic call but incomplete for nuanced usage.

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%, so the description must compensate. It explains min_impressions, max_position, and limit with clear semantics, but it leaves days, end_date, start_date, and site_url unexplained. This partial coverage adds value for the core parameters but leaves a significant portion of the schema undocumented, making it insufficient for full parameter comprehension.

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 what the tool does: it identifies queries that rank well but get fewer clicks than expected, framing them as CTR opportunities. It distinguishes itself from generic ranking tools by specifying the focus on title/meta-description problems. However, it doesn't explicitly name sibling tools like gsc_striking_distance, so the differentiation is implicit rather than explicit.

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 the tool should be used when looking for low-hanging wins in CTR, but it provides no explicit guidance on when to use it versus alternatives like gsc_striking_distance or gsc_top_queries. There is no 'use when' or 'don't use when' clause, leaving the agent to infer the appropriate context from the problem framing.

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