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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint false, so the safety profile is covered. The description adds value by disclosing that GSC must be connected and providing a specific integration URL, plus explaining the strategic context behind the query results. No contradiction with annotations.

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 four sentences, front-loaded with the core purpose in the first sentence. Each subsequent sentence earns its place: the 'ranking but not clicked' explanation, the ROI rationale, and the prerequisite/instruction. There is no redundant content.

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?

With six well-documented parameters and no output schema, the description adequately covers the tool's purpose, usage context, and prerequisite. It could mention what the return data looks like, but the self-explanatory name and rich schema make the description sufficiently complete for an agent to select and invoke the tool correctly.

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 input schema has 100% coverage with detailed descriptions for all six parameters (site, startDate, endDate, maxCtr, rowLimit, minImpressions). The description does not add parameter-specific meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 'Find search queries with high impressions but low CTR' with a specific verb and resource. It distinguishes from sibling tools like get_gsc_low_ctr_pages by focusing on queries rather than pages, and adds context by explaining these are 'ranking but not getting clicked'.

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 gives clear usage context: these queries are underperforming in clicks despite high impressions, and fixing them is 'typically higher ROI than chasing new rankings.' It also notes the prerequisite that Google Search Console must be connected, with a direct URL for setup. However, it doesn't explicitly mention when not to use this tool or name alternative tools, so it stops short of a 5.

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