get_search_by_page_query

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

With no annotations, the description carries the burden. It discloses important behavior: site_url must come from list_properties, domain properties cover all subdomains, and row_limit has max. It also explicitly mentions pagination limitations. This adds meaningful context beyond what the schema provides, though it doesn't cover error handling or rate limits.

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 well-structured with a concise summary line followed by an Args block. Every sentence is informative, no filler, and the layout makes it easy to scan. It's appropriately sized for the tool's complexity.

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 the tool's 4 parameters, output schema exists, and no annotations, the description is thorough: it covers purpose, param semantics, scope definitions, and alternative tools. It provides enough context for an agent to invoke this tool correctly without needing extra clarification.

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%, so the description fully compensates by explaining each parameter with examples, defaults, and usage tips (e.g., site_url formatting, row_limit ranges). This goes well beyond the bare schema and makes the parameters self-explanatory.

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 clearly states the tool's function: 'Get search analytics data for a specific page, broken down by query.' This is a specific verb+resource+scope, distinguishing it from the general search analytics tools and other siblings.

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 provides context on when to use this tool (for a specific page, broken down by query) and explicitly points to get_advanced_search_analytics for bulk exports beyond 500 rows. It doesn't explicitly contrast with get_search_analytics, but the alternative guidance and row_limit suggestions offer clear usage context.

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