get_search_analytics

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

With no annotations, the description carries the burden of behavioral disclosure. It does reveal the returned metrics and that omitting dimensions yields both top queries and top pages. However, it does not describe the output structure, pagination, or how the results are organized when dimensions are supplied, leaving some behavioral ambiguity.

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 two sentences with no filler. The first sentence front-loads the core action and result metrics, and the second sentence usefully clarifies the default dimension behavior.

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?

The description plus fully documented schema provide enough to make a basic call correctly. However, with no output schema, the description should explain the shape of the returned data more fully; it names metrics but not whether the response is a flat list, grouped arrays, or paginated.

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 100%, and the schema already documents every parameter thoroughly, including date-lag behavior and siteUrl format. The description's only added parameter insight is the default behavior for the `dimensions` array, but the schema already states 'Omit to get both top queries and top pages.' Thus the description adds little beyond the 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 names a specific verb and resource ('Get top search queries and pages') and the metrics returned (clicks, impressions, CTR, average position), so an agent can tell what the tool does. It also notes the default grouping behavior, but it does not explicitly contrast this tool with sibling tools like get_advanced_search_analytics or get_search_by_page_query.

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?

There is no guidance about when to choose this tool over alternatives such as get_advanced_search_analytics or get_performance_overview. The description implies it is for search analytics reporting, but it never states prerequisites, exclusions, or conditions that would route an agent to a sibling tool.

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