Search performance (custom)

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

Annotations already declare readOnlyHint=true, covering the safety profile. The description adds that it can optionally compare with the previous period, which is a behavioral detail, but it does not disclose output format, pagination, or rate limits. It does not contradict annotations.

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 a single, dense sentence that front-loads the purpose and then lists capabilities. Every phrase earns its place, with no redundancy or filler.

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 query tool with no output schema, the description covers the primary features but omits details like sorting and limits, which are available in the schema. It is functional but not exhaustive for a tool with 8 parameters.

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 only 50%, and the description compensates for key parameters like group_by (lists grouping dimensions), filter_page/filter_query ('filter by text'), and compare_previous ('compare with the previous period'). It does not add value for sort_by or limit, but those have defaults and enums, so the partial compensation is adequate.

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 identifies this as a flexible Search Console query for performance data, listing grouping, filtering, and comparison options. It is specific enough to distinguish from siblings like site_overview, though it does not explicitly name alternatives.

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 implies usage through its listed capabilities (grouping, filtering, comparing) but gives no explicit guidance on when to use this tool over siblings like site_overview or find_opportunities. An agent can infer when it is appropriate, but there are no exclusions stated.

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