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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, covering the safety profile. The description adds meaningful context beyond annotations: the Google Search Console connection requirement, the exact integration URL for the user, and how multi-account property resolution works.

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?

Front-loads the purpose, then adds prerequisite and account-resolution details. Four sentences, each serving a purpose; the integration URL sentence is operational guidance rather than filler, though it could be slightly tighter.

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 breakdown tool with no output schema and rich annotations, the description covers purpose, prerequisite, and multi-account behavior. It does not describe the return shape in detail, but the phrase 'Shows which search features are driving impressions and clicks' gives adequate orientation.

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 100%, so all three parameters (site, startDate, endDate) are fully documented in the schema. The description adds no additional syntax, format, or constraint details beyond what the schema already provides.

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?

States a specific verb ('Break down traffic') and resource ('how the site appears in Google Search'), and enumerates the dimensions (organic, rich results, AMP, image, video, news). Clear enough to distinguish it from generic GSC reports, but it does not explicitly name or contrast with sibling breakdown tools like country or device breakdowns.

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?

Implies usage by describing the value ('Shows which search features are driving impressions and clicks') and states a hard prerequisite (GSC must be connected). Does not state when to prefer this tool over alternatives such as get_gsc_country_breakdown or get_gsc_device_breakdown.

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