search_analytics

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

With no annotations provided, the description must fully disclose behavioral traits. It only says 'Run a flexible Search Analytics query' without mentioning read-only nature, rate limits, authentication, or result format. This is almost no disclosure beyond the name.

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 very short (2 sentences, 16 words). It is not verbose, but it sacrifices informativeness. While structured well, it lacks depth. A slightly longer description with key details would be more helpful without being wasteful.

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 complexity (10 parameters, many enums, no output schema, no annotations), the description is grossly incomplete. It fails to explain return format, pagination, metric types, or behavior of aggregation and search type. This is insufficient for correct invocation.

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 50%, meaning 5 of 10 parameters lack schema descriptions. The description adds 'custom dimensions and filters' which partially covers dimensions and filters, but does not explain other undocumented parameters like searchType, dataState, aggregationType, or rowLimit. It provides minimal extra meaning.

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 verb 'Run' and the resource 'Search Analytics query', and indicates it allows 'custom dimensions and filters'. This makes the purpose specific, though it does not explicitly differentiate from sibling tools like 'dimension_breakdown' which may overlap.

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 says 'Use this for exact data pulls with custom dimensions and filters', implying when to use. However, it provides no guidance on when not to use or mention of alternative tools, leaving room for ambiguity given the large sibling list.

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