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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description adds genuinely non-obvious behavior: the GSC connection prerequisite and how multi-account ambiguity is resolved ('read through the account that can see it'). Missing return-shape details, but that is not required here.

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?

Three sentences, front-loaded with the core purpose, followed by the prerequisite and the multi-account edge case. The integration URL is a little instrucional, but each sentence carries distinct value and there is no filler.

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?

There is no output schema, and the description never indicates what a breakdown row contains (metrics such as clicks, impressions, CTR, position). For a reporting tool whose return shape is not self-evident, that is a real gap, though the prerequisite and account-resolution notes cover the invocation side well.

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% with three fully documented required parameters (site, startDate, endDate), so the schema carries the load and a 3 baseline applies. The description adds nothing about date-range semantics, timezone, or how the site URL should be formatted.

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 (search traffic by device type) and enumerates the dimension values (desktop, mobile, tablet), which cleanly separates it from sibling breakdowns like get_gsc_country_breakdown and get_gsc_date_trends. An agent can select it without opening the schema.

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?

Gives an explicit precondition (Google Search Console must be connected) and a remediation path (direct the user to rankparse.com/dashboard/integrations). It does not, however, say when to prefer this breakdown over the country/date/appearance siblings, so the routing guidance is partial.

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