get_search_by_page_query

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

No annotations are provided, so the description carries the burden. It clearly implies a read operation (getting data) and explains parameters in detail, but it does not explicitly declare read-only behavior or mention permissions. For a simple search analytics retrieval, this is largely sufficient, though a note on non-destructiveness would be beneficial.

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?

Description is front-loaded with a clear purpose statement, followed by well-structured parameter explanations in bullet-like format. Each sentence is informative and necessary, with no redundancy.

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 has 4 parameters, an output schema (so return values are covered), and no annotations, the description covers all parameters with useful context. It could mention the output's scope (e.g., aggregated query data) but is largely complete for effective use.

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 fully compensates: for site_url it provides examples and domain property vs page filtering explanation; for row_limit it offers usage ranges and scenarios; for days it explains default and purpose; for page_url it clearly defines. This adds significant meaning 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?

Description explicitly states 'Get search analytics data for a specific page, broken down by query.' This clearly distinguishes it from sibling tools like get_search_analytics (broader) and get_advanced_search_analytics (paginated).

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: explains domain property usage for site_url, recommends filtering by page for subdomain analysis, and for row_limit gives usage scenarios and explicitly cites get_advanced_search_analytics for bulk exports beyond 500 rows. This is a clear when/when-not/alternatives pattern.

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