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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds two useful behavioral facts beyond the annotations: the query is restricted to a whitelist of families, and it operates on exactly one customer. It says nothing about result caps, latency, or rate limits, so the added value is real but thin.

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 front-loaded sentence with no filler or redundancy. It is efficient, though the brevity reflects under-specification rather than disciplined editing.

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 7-parameter analytical query with no output schema, an opaque "whitelist" concept, and a sibling tool dedicated to listing valid families, the description leaves the agent without the information needed to construct a correct call. The read-only annotations cover safety, but the operational guidance is missing.

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 29% across 7 parameters: only customer_id and detail_level are documented, leaving family, date_from, date_to, limit, and connection_context unexplained in both schema and description. The description names no parameters and only obliquely implies the single-customer scope, so it fails to compensate for the coverage gap.

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?

The description gives a verb ("Run") and a resource ("deep-analysis query") scoped to one customer, which is more than a tautology. However, "whitelisted" is left unexplained, and it does nothing to distinguish this tool from close siblings like google_ads_analysis_families_list, google_ads_deep_analysis_export, or google_ads_insights_query_daily. An agent cannot tell from this sentence alone when this tool is the right one.

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?

There is no when-to-use guidance, no mention of the prerequisite step of discovering valid `family` values (a sibling tool exists for that), and no routing to the export variant or the insights query siblings. The word "whitelisted" hints at a constraint but does not tell the agent what is allowed or how to satisfy it.

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