webmaster_list_popular_queries

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

No annotations; description implies read-only ('read') and a 31-day max period, but omits side effects, permissions, pagination behavior, and error/empty results.

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?

One compact sentence with no filler, but the phrase 'explicit periods are at most 31 days' is slightly awkward and would benefit from clearer structure.

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 8 parameters and no schema descriptions, the description leaves many functional details unexplained; output schema exists, but request semantics are under-specified.

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 has 8 params with 0% description coverage; description does not explain host_id, limit, offset, order_by, query_indicator, device_type_indicator, or date formatting.

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 it reads a page of popular queries, indicating action and resource, but does not clarify how this differs from webmaster_get_query_history or define 'popular 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?

No guidance on when to use this over sibling tools; only mentions a date-range limit, not selection criteria or alternative tools.

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