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

With readOnlyHint already declared, the description adds genuinely new behavioral context: the history window (16 months for paid domains, 3 months otherwise), the auth precondition of a connected Search Console account, and the localization behavior (responses follow the account language, German by default). These are things an agent could not learn from annotations or schema and would otherwise guess wrong about.

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?

Every sentence carries information: purpose first, then use cases, then the exact-match constraint, then the tier limits, then the auth requirement, then localization. No restatement of the name or filler, and the highest-value detail (what the data is) leads.

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?

There is no output schema, and the description compensates by naming exactly what comes back (clicks, impressions, impression-weighted position, plus ranking pages). Combined with the tier-based lookback limits and auth prerequisite, an agent has everything needed to call it correctly 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 100%, so the baseline is 3; the description improves on it by stressing that the query must be passed exactly as Search Console lists it, which constrains how an agent should populate that string. It also reinforces the months semantics (16 paid / 3 free) that the schema only partly conveys. It adds meaning beyond the schema without fully documenting it.

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: month-by-month history of a single keyword from Google Search Console, including metrics and the pages ranking for it. This is clearly distinguishable from sibling tools like search_console_queries (which covers many queries) or search_console_pages, because it is the per-keyword deep-dive tool. An agent can tell what it returns without opening the 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 when to reach for it: to see how a query developed, whether it is seasonal, or which page Google shows for it. It also states the gating prerequisite (the user must have connected Search Console). It does not name an alternative sibling for the broad-listing case, which keeps it below a 5.

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