dimension_breakdown

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

With no annotations provided, the description carries full burden but only states what it does, not behavioral traits. No mention of read-only nature, data latency, or response structure, which is critical for an agent to invoke safely.

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?

Single sentence is concise and front-loaded with the core action. However, it could benefit from additional context without becoming verbose.

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 7 parameters, no output schema, and 38 sibling tools, the description is too sparse. Does not explain return format, aggregation behavior, or prerequisite knowledge (e.g., siteUrl format).

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 coverage is 71%, meaning most parameters have descriptions in the schema. The description adds minimal value beyond listing example dimensions; it does not clarify the use of 'filters' or the 'limit' parameter.

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?

Description clearly states verb ('break down') and resource ('performance by a single dimension'), with examples of dimensions. However, it does not differentiate from siblings like 'search_analytics' or 'top_pages', which also query performance data.

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?

No guidance on when to use this tool versus alternatives such as 'search_analytics' or 'page_query_matrix'. Lacks context about when a single dimension breakdown is preferable to multi-dimensional queries.

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