get_search_by_page_query

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

With no annotations provided, the description carries the behavioral disclosure burden. It clearly implies a read-only analytics operation and transparently discloses the 500-row limit with a pagination alternative. However, it does not mention potential rate limits, exact-match requirements, or behavior when no data exists for a page, which would be useful completeness.

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 efficiently structured as a one-line purpose followed by an Args list. Every sentence adds value: parameter explanations, defaults, usage intervals, and a sibling reference. There is no filler or repetition of schema data.

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 moderate complexity and the existence of an output schema, the description covers all necessary invocation context: required parameters, optional parameters with defaults, max limit, usage guidance, and a pointer to an alternative for larger exports. It is fully sufficient for an agent to call this tool correctly.

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%, so the description fully compensates by explaining every parameter in depth: site_url with property URL formats and domain-property nuance, page_url as a specific page, days with default, and row_limit with practical ranges and a hard max. This goes far 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 opens with 'Get search analytics data for a specific page, broken down by query,' which names a specific verb, resource, and scope. This clearly distinguishes it from sibling tools like get_search_analytics and get_advanced_search_analytics without needing to inspect their schemas.

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 explicit guidance on when to use this tool vs alternatives: it advises using the domain property as site_url and filtering by page for subdomain analysis, and it directs users to get_advanced_search_analytics for bulk exports beyond 500 rows. The row_limit usage ranges also give situational recommendations.

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