get_advanced_search_analytics

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

No annotations are provided, so the description must fully disclose behavioral traits. It explains the filter format but omits side effects, authentication requirements, rate limits, or error handling. The required parameters are not highlighted, leaving the agent uninformed about essential inputs.

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 with only two sentences and an example, no redundant text. The filter format is front-loaded, making it easy to parse. However, it could be slightly expanded to cover key parameters without becoming verbose.

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 7 parameters, an output schema, and multiple sibling tools, the description is insufficient. It lacks context on when to use this versus similar tools (e.g., get_search_analytics), required parameter rationale, and return value expectations (though output schema may cover the latter). The description feels incomplete for effective agent usage.

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 coverage is 0% (no parameter descriptions), so the description must compensate. It adds meaning only to the filters parameter with format and operator examples, but fails to describe the other six parameters (account, end_date, site_url, row_limit, dimensions, start_date). This leaves most parameters ambiguous.

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 provides advanced search analytics with dimension filters, using a specific verb ('get') and resource ('advanced search analytics'). It distinguishes from siblings like 'get_search_analytics' by implying enhanced functionality, but lacks explicit differentiation.

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 includes a filters format and list of operators, offering usage guidance for the filters parameter. However, it does not specify when to use this tool over alternatives like get_search_analytics or get_performance_overview, nor does it mention prerequisites or context.

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