webmaster_list_popular_queries

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful context beyond that — pagination ('one page') and the 31-day period ceiling — but does not elaborate on auth needs or result behavior.

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?

A single front-loaded sentence with no wasted words, and the scoping constraint is placed after the core action. Efficient, though the brevity leaves it thin for an 8-parameter tool.

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?

An output schema exists (so return values needn't be explained) and annotations cover safety, but with 8 parameters at 0% schema coverage and several sibling analytics tools, the description is too sparse to fully guide selection and invocation.

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 0% across 8 parameters, so the description must carry the burden. It only clarifies the date range parameters via the 31-day constraint and hints at limit/offset with 'one page'; host_id, order_by, query_indicator, and device_type_indicator remain entirely undocumented.

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 clear verb (Read) and resource (popular queries) with a pagination note. However, it does not differentiate this tool from siblings such as webmaster_get_query_history, webmaster_query_analytics, or yandex_wordstat_get_top, which an agent must choose between.

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 'explicit periods are at most 31 days' clause gives an implied usage constraint and 'one page' signals a paginated listing. But there is no explicit when-to-use/when-not guidance and no naming of the alternative query-analytics tools.

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