get_performance_overview

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

With no annotations provided, the description carries the behavioral disclosure burden. 'Get a performance overview' implies a read-only operation, and the description adds detail about domain property coverage. However, it does not mention what the overview contains, whether it requires special permissions, or what the response shape is; the output schema helps but is not described here.

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 compact and front-loaded with the core purpose, followed by a concise parameter explanation. Every sentence contributes useful information and there is no filler or repetition of the schema.

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 read-only overview tool with a simple two-parameter schema and an output schema available, the description is largely sufficient. It covers parameter semantics and usage context well. The only notable gap is that 'performance overview' is not defined, so the agent must rely on the output schema or tool name to infer metrics like clicks, impressions, CTR, or position.

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%, so the description must fully compensate. It explains that site_url should be an exact GSC property URL from list_properties, gives concrete examples, clarifies that domain properties cover all subdomains, and explains how to analyze a specific subdomain. It also gives the meaning and default of days. This fully covers both parameters.

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 clear verb and resource: 'Get a performance overview for a specific property.' It is not as specific as sibling names like get_search_analytics or get_advanced_search_analytics, but it is not a tautology and gives the agent a reasonable idea of the operation.

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 useful context on how to supply site_url, including the distinction between URL-prefix and domain properties and how to handle subdomains. However, it does not explicitly say when to use this tool versus alternatives like get_search_analytics, get_advanced_search_analytics, or compare_search_periods.

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