get_search_by_page_query

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

With no annotations, the description carries full burden. It discloses behavioral traits: domain properties cover subdomains (filter by page for subdomain analysis), row_limit max 500 with pagination alternative. It does not explicitly state read-only nature but it is implied. No contradictions.

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 front-loaded with a clear purpose statement. Every sentence serves a purpose – parameter explanations, usage tips, alternative tool reference. No wasted words despite being detailed.

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 4 parameters, output schema existence, and sibling tools, the description covers parameters well and mentions an alternative tool. It does not describe the output structure (though output schema handles that) or authentication requirements, which are standard and can be inferred.

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 description coverage is 0%, but the description provides thorough inline parameter guidance: site_url (example, domain property behavior), page_url (specific page), days (default 28), row_limit (ranges, max, alternative). Each parameter gains meaningful context beyond the bare schema.

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 purpose: 'Get search analytics data for a specific page, broken down by query.' This verb+resource+scope formulation distinguishes it from siblings like get_search_analytics (likely overall data) and get_advanced_search_analytics (bulk pagination).

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?

Provides explicit guidance: site_url format (with domain property subdomain coverage), page_url requirement, row_limit ranges (5-20 overview, 50-200 analysis, up to 500 comprehensive), and clearly names get_advanced_search_analytics as the alternative for bulk exports beyond 500 rows.

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