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

Annotations already declare this read-only, idempotent, non-destructive, and closed-world, so the safety profile needs no restating. The description adds the payload shape (coverage %, delta vs previous run, intent buckets, keyword states) but no behavioral context such as freshness, time window, or what 'previous run' means.

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?

A single tight sentence that front-loads the resource and then lists return dimensions with no filler. Efficient, though the dense parenthetical list is slightly harder to parse than separate clauses.

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 one-parameter read tool with strong annotations but no output schema, the description usefully compensates by enumerating the returns rather than leaving them opaque. The main gap is the unresolved overlap with get_ai_visibility.

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?

One parameter with 100% schema description coverage ('UUID of the site'), so the schema fully documents it. The description adds nothing about site_id scope or format, which is the expected baseline when the schema does the work.

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 ('Google AI Overview coverage for a site') and enumerates the returned dimensions. Clear enough to act on, but it never distinguishes itself from the sibling 'get_ai_visibility', which sounds adjacent and could confuse selection.

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 when-to-use, when-not-to-use, or alternative is offered. With 'get_ai_visibility' in the sibling list, the reader must guess which endpoint answers their question; the description provides no routing help.

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