gsc_analyze_search_appearance_trends

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

With no annotations and no output schema, the description carries the full transparency burden. It only warns that the searchAppearance dimension may not be exposed; it does not disclose how trends are computed, what the return shape is, or behavior around limits, missing data, or the comparison periods.

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?

A single front-loaded sentence with no filler; the core purpose and a key caveat are presented immediately. The description earns its place despite being short.

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?

For a 10-parameter tool with no annotations and no output schema, this description is under-specified. It omits default comparison behavior, output shape, sort semantics, page-level grouping effects, and how the current vs previous period comparison works, leaving important aspects of a correct call undefined.

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 low (40%), so the description needs to add meaning. It adds useful context by naming the searchAppearance dimension and the trend-analysis focus, which helps explain delta-based sort and date-range parameters, but it leaves several parameters like topN, limit, minImpressions, and searchType effectively undocumented.

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 states a specific action (analyze) and a specific resource/dimension (Search Analytics searchAppearance) with a clear focus on structured data and rich-result trend signals. It distinguishes the tool from generic query analytics by naming the exact dimension, though it does not explicitly name a sibling alternative.

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 phrase 'when GSC exposes it' implies a precondition for use, and 'rich-result trend signals' implies the intended scenario. However, the description gives no explicit guidance on when to choose this tool over alternatives such as gsc_query_search_analytics or gsc_compare_search_types, so the agent must infer selection.

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