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

readOnlyHint already marks this as a safe read; the description adds genuinely non-obvious context: the user must have connected Search Console, and responses come back in the account language (German by default). It does not mention the 25-row cap, pagination, or freshness of the underlying data.

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?

Four sentences, front-loaded with the resource and scope, then the intent semantics, then the prerequisite and language caveat. Nothing is repeated from the schema and nothing feels like padding.

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 does enough: it defines the report shapes per intent, the precondition, and the language of results. A brief note on what a row contains (keyword, position, clicks) and the row cap would close the remaining gap.

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, but the description adds real meaning by defining what each intent value returns rather than restating the enum. window and limit are left to the schema, which already documents them adequately.

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?

Names a specific resource (keyword data from Google Search Console) scoped to one domain, and the three intent modes give the agent a precise picture of what comes back. It never names search_console_pages or keyword_history, so differentiation from siblings is only implicit.

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 intent definitions effectively say which report to pick for which goal (strongest keywords vs. positions 5-20 vs. winners/losers), and the Search Console connection prerequisite is stated. But there is no guidance on when to choose this tool over search_console_pages or keyword_history, which are the closest alternatives in the sibling set.

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