search_console_analytics_device_breakdown

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

With no annotations provided, the description carries the full burden. It only says 'Get device breakdown for a site' without disclosing return format, default row limit, or specific behavior. The shortcut reference to analytics.query adds some context, but it doesn't describe what the response looks like or any limitations.

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?

Two sentences, front-loaded with the core purpose and a concise explanation of its relationship to the general query tool. No redundant information or fluff.

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?

The description is minimal but includes a useful reference to analytics.query, which helps an agent infer that input and output behaviors align with that tool. However, without annotations or an output schema, the description could be more explicit about return values and required site_url usage. It's adequate but leaves some gaps.

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?

The input schema has 100% coverage with descriptions for all four parameters. The tool description does not add any parameter-specific guidance, but since the schema already documents each parameter adequately, the baseline score of 3 is appropriate.

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 'Get device breakdown for a site' with a specific action and resource. It additionally distinguishes itself by noting it's a shortcut for analytics.query with dimensions=['device'], which separates it from the general query tool and other breakdown tools.

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 indicates this is a shortcut for analytics.query, implying it's the right choice when you specifically need device breakdown without writing the full query. It doesn't explicitly mention when not to use it or compare with other breakdown tools like top queries or top pages, but the context is relatively clear.

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