ctr_opportunities

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

With no annotations, the description fully carries the behavioral disclosure burden and does so thoroughly. It warns that position is an impression-weighted average, not a rank-tracker rank, that deep positions rely on sparse data, and that absolute positions are directional. It also instructs the agent to base analysis only on returned data, report exact numbers, and avoid speculation, which is valuable behavioral guidance.

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 longer than average but well organised into purpose, analysis constraints, presentation requirements, and position semantics. Each section contributes useful guidance, though the presentation block is somewhat verbose relative to the core tool purpose.

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 is thorough about methodology, caveats, and output presentation despite the absence of an output schema. It does not explicitly list the exact fields returned by the tool, which would be helpful, but the core instructions and position caveats give the agent enough to invoke the tool correctly and interpret results safely.

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 100%, so the schema already documents both parameters and their defaults. The description adds no additional parameter-level detail, which is acceptable at the baseline score of 3.

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 states a specific verb and resource: 'Find pages with high impressions but CTR significantly below expected for their position', and labels them as title/meta description optimisation candidates. This clearly identifies what the tool does and distinguishes it from the sibling ctr_vs_benchmark by anchoring on expected CTR for position.

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?

It provides clear context: use this tool when looking for pages that combine high impressions with weak CTR, specifically for title and meta description optimisation. It does not explicitly name sibling tools to avoid or give when-not-to-use conditions, but the purpose statement is specific enough to imply the correct use case.

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