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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds genuinely new behavioral context: restricted services demand fresh server-verified access and will refuse otherwise, and no writes or access grants occur. It stops short of defining what 'restricted' or 'fresh' mean, but it clears the lower bar set by 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?

Three tight sentences with the core read purpose front-loaded, followed by the access constraint and the no-write guarantee. Slightly jargon-heavy ('bounded native', 'fresh server-verified'), but nothing is padded.

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?

No output schema exists and the input contains a required nested object with an enum-constrained dimension list, yet the description explains neither the request body shape nor the returned insight. For a tool with this schema complexity, the description leaves too much for the agent to infer.

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 only 33% — just customer_id is documented — and the description adds nothing about the nested body object, its required dimensions/query_text fields, the five-item dimension cap, or connection_context. With low coverage the description is expected to compensate and it does not.

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 (Read) and resource (native audience_attributes insight), which maps directly onto the tool name and distinguishes it from sibling data tools such as google_ads_audience_dates and google_ads_insights_overview_query. It does not, however, explain what the insight actually contains or how it differs from the other insight/audience siblings, so the differentiation is only implicit.

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?

The description gives an access precondition ('Restricted services require fresh server-verified access and otherwise refuse') but never says when to choose this tool over the many sibling insight and audience tools, nor when not to use it. Usage is only implied by the resource name.

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