Top pages by clicks

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the bar is lower. The description still contributes a non-obvious behavioral fact — the data lag ('ending three days ago') — which the agent needs to interpret freshness correctly, though it says nothing about pagination, rate limits, or how limit interacts with large result sets.

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?

Two sentences with no filler: the first front-loads what is returned, the second front-loads the default time window. Nothing is repeated from the title or annotations.

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?

For a 7-parameter analytics tool with no output schema, the description does list the returned measures, which partially substitutes for a return schema. However, it omits how limit/pagination behaves, how this differs from query_search_analytics or top_queries, and any prerequisite such as needing a verified property, leaving meaningful gaps.

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 71%, so the schema already documents site, type, account, country, and query_filter, including the 403 warning for mismatched property shapes and the error behavior for discover/googleNews. The description only adds semantics for the date window (days default 28, ending three days ago) and leaves limit entirely undocumented in both places, so it compensates only partially.

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 (pages on a property) and the ranking metric (most clicks from Google Search), plus the returned measures (impressions, CTR, average position). An agent can distinguish this from the sibling top_queries without opening either schema, since one ranks pages and the other ranks queries.

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 states the default reporting window ('last 28 days ending three days ago'), which is useful context, but gives no explicit when-to-use or when-not-to-use guidance against alternatives such as top_queries, compare_periods, or query_search_analytics. Usage is implied by the resource name rather than stated.

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