gsc_query_devices

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering safety and side effects. The description adds no additional behavioral context such as pagination, date-range constraints, or how the grouping affects results. It only restates what is evident from the tool 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 a single, concise sentence free of unnecessary words. It front-loads the core purpose efficiently with no fluff, making it highly scannable for an agent.

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 9 parameters, no output schema, and a minimal description, the agent has insufficient context to understand return formats, how to properly set dimensions, or how this tool relates to the broader Search Analytics suite. The description is far too sparse for the tool's complexity.

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 very low (11%), with only siteUrl described. The description mentions 'device' but does not explain how to configure the dimensions parameter or any other parameters. It fails to compensate for the lack of schema descriptions, leaving most parameters underspecified.

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 'Query Search Analytics grouped by device' clearly states the action (query), the resource (Search Analytics), and the specific grouping (device). It distinguishes this tool from siblings such as gsc_query_queries, gsc_query_pages, and gsc_query_countries by specifying the device dimension.

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 no explicit guidance on when to use this tool versus alternatives. It does not mention use cases, prerequisites, or mention sibling tools. The usage is only implied by the tool name and description.

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