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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds genuinely new behavioral context: the auth/connection requirement, the dashboard URL for remediation, and how the property is resolved when multiple Google accounts are connected. It doesn't describe response shape, but that is a minor gap given the 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?

Front-loads what the tool does, then follows with prerequisite and account-resolution notes; each sentence is functional. Slightly more prose than strictly necessary, but no waste.

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?

With no output schema, the description does state what comes back (which search features drive impressions and clicks) and covers the setup dependency. It is complete enough for a 4-param read tool, though a hint about row grouping or dimensions would round it out.

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 100%, so site, startDate, endDate, and the searchType enum are fully documented in the schema, including the caveat about googleNews/discover not supporting query. The description names the appearance dimensions but adds no format or usage detail beyond the schema, so the baseline 3 applies.

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 and resource: breaking down traffic by how the site appears in Google Search (rich results, AMP, image, video, news). This clearly distinguishes it from sibling breakdowns like get_gsc_device_breakdown and get_gsc_country_breakdown without needing to inspect schemas.

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?

Provides a concrete prerequisite (Google Search Console must be connected) and tells the agent to direct the user to rankparse.com/dashboard/integrations, plus explains multi-account property resolution. It does not, however, explicitly contrast with alternatives like get_gsc_top_queries or get_gsc_date_trends, so an agent must infer when this breakdown is the right choice.

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