top_pages

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

No annotations are provided, so the description must fully disclose behavioral traits. It fails to mention output format, pagination, aggregation level, or whether the tool is read-only. The description is too brief to cover necessary transparency for safe invocation.

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?

The description is a single sentence, making it concise and front-loaded. While it could be slightly more informative without losing conciseness, it efficiently conveys the core purpose.

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?

Given 7 parameters, 38 sibling tools, and no output schema, the description is insufficient. It lacks details on return values, parameter interactions, and differentiation from similar tools, leaving the agent underinformed for correct selection and usage.

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?

With 71% schema description coverage, the schema already documents most parameters. The description adds only a mention of 'optional query filtering' corresponding to 'queryContains', but does not enhance understanding of other parameters like 'minImpressions' or 'limit' beyond what the schema provides.

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?

The description uses a specific verb 'Find' and resource 'top pages', clearly stating the tool's function. It mentions optional query filtering and a use case ('landing page and folder audits'), which helps differentiate from some siblings like 'top_queries' but could be more explicit about what 'top' means (e.g., by impressions or clicks).

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 implies usage for landing page and folder audits, providing some context. However, it does not explicitly state when to use this tool versus alternatives like 'top_queries' or 'search_analytics', nor does it specify when not to use it.

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