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

Annotations already cover the safety profile (readOnlyHint, non-destructive, openWorld). The description adds genuine behavioral context beyond them: it queries Search Console impressions, requires a caller-supplied URL list because Caybl tracks none, and normalizes scheme (http/https) and trailing-slash variants automatically. It omits return shape and rate/pagination limits, but those are secondary here.

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 purpose is front-loaded in the first sentence and each following clause carries information (why `urls` is required, URL-variant matching). It is somewhat dense and long-winded, but little of it is filler, so it stays efficient despite the length.

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 no output schema, the description usefully states what is returned (which supplied URLs got zero impressions). It justifies the required parameter and the loose URL matching, which are the non-obvious details for correct invocation. Date-window semantics are left to the schema, which is acceptable at this complexity.

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 coverage is 75%, so the schema already documents the main parameters. The description adds real meaning for `urls` (the caller's tracked page list, matched loosely against Search Console forms), but says nothing about startDate/endDate/siteUrl beyond what the schema provides. Baseline 3 is appropriate given the schema does most of the lifting.

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 names a specific verb (find/return which) and resource (tracked pages with zero Search Console impressions over a window), so an agent can tell what it produces. It stops short of naming a sibling alternative (e.g. inspect_url, run_search_analytics_report) to distinguish itself explicitly, so it lands just below the top tier.

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 gives clear context for when to reach for this tool: diagnosing a suspected indexing problem ('manual indexing check... rather than assuming it's simply low demand'). It also explains why the caller must supply URLs. No explicit when-not or named alternative is provided, keeping it at 4 rather than 5.

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