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 behavioral disclosure burden. It explains row_limit max of 500, the pagination limitation, and how domain properties work, but it does not explicitly state whether the operation is read-only or mention any rate limits or auth requirements. The provided context is useful but not exhaustive.

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 concise, organized as an Args block, and every sentence adds practical value. It avoids redundancy and keeps the content tightly scoped to the tool's operation.

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 presence of an output schema, the description covers all necessary input semantics and the key limitation (500-row cap). It provides enough context for an agent to select and invoke the tool correctly, including when to use an alternative.

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 by explaining each parameter: site_url format with sc-domain example, page_url purpose, days default, and row_limit semantics with recommended ranges. This goes well beyond the raw 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 gets search analytics data for a specific page, broken down by query, using a specific verb and resource. It distinguishes itself from siblings by noting that bulk exports beyond 500 rows should use get_advanced_search_analytics.

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 when-to-use guidance, including suggested row_limit ranges (5-20 quick overviews, 50-200 deeper analysis, 500 comprehensive) and points to get_advanced_search_analytics as the alternative for paginated bulk exports. It also clarifies domain property coverage and filtering by page.

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