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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds two genuinely useful behavioral facts beyond the schema: the data is only available "when connected" (an integration/availability prerequisite) and lags about 2 days, which materially affects date-range expectations. It stops short of noting pagination or response shape.

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 with zero filler: the first front-loads what data is returned and at what grain, the second delivers the freshest-operating constraint (2-day lag). Nothing is repeated from structured fields.

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 carries the return-value burden and does reasonably well by naming metrics, dimensions and the daily series. It does not describe pagination behavior or how limit/default 10 shapes the response, which is a minor residual gap for a 10-parameter tool.

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 90%, so the schema already documents dates, period, limit, filters, timezone and segment_id in detail. The description's mention of "by query, page, country or device" and the daily series loosely maps to the dimension parameter but adds no syntax or default information beyond the schema. Baseline 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?

States a specific verb/resource — Google Search Console data for a site — and enumerates the metrics (clicks, impressions, CTR, average position) and breakdown dimensions (query, page, country, device) plus a daily series. This clearly separates it from generic analytics siblings like get_breakdown or get_pages, though it never names a sibling explicitly.

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?

"when connected" implies a precondition and the scope is clear, but there is no explicit when-to-use vs. alternative guidance (e.g. when to prefer this over get_breakdown / get_pages for the same site). Usage is only inferable from the metric list.

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