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

With no annotations, the description carries the full burden and does well: it discloses live-fetch latency vs the cached sibling, that total_available is null because the API does not report row counts, and the truncated/next_offset paging contract. It does not cover permissions or rate/quota limits, which are relevant for a live Search Console call.

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?

Long but front-loaded and clearly segmented with POSITION and PAGING headers, so the routing guidance comes first. Dense rather than padded, though the paging paragraph could be tightened.

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?

No output schema exists, so the description must explain return semantics, and it does: the pagination block fields, null total_available, truncated logic, and impression-weighted position interpretation. An agent has everything needed to call and interpret the result.

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 88%, so the schema already documents days, offset, filters, order_by, row_limit, dimensions and order_direction. The description reinforces offset/truncation behavior but adds little per-parameter meaning beyond what the schema provides; baseline 3 applies.

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?

States a specific verb+resource ('the raw cut of Search Console data') with the scope made explicit: any dimensions, filters, sort, fetched live for this call only. It names the sibling Keyword_Rankings and how it differs, so an agent can distinguish it without opening either schema.

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?

Explicitly says to prefer Keyword_Rankings when a preset window is enough and to reach for this only when the question needs a window, filter or dimension combination the cache does not expose. The alternative and the selecting condition are both named.

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