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

No annotations are provided, so the description must carry the behavioral disclosure burden. It only says 'run a whitelisted deep-analysis query,' which implies a read operation but does not state whether it is read-only, what it returns, what 'whitelisted' entails, or how it behaves on errors or large result sets.

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?

The description is a single, front-loaded sentence with no filler or redundant restatement of the tool name. Every word contributes a basic constraint, making it highly concise and easy to parse.

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 six-parameter tool with no output schema and no annotations, this description is far too thin. It does not explain what a 'deep-analysis query' is, how to choose a family, what date range semantics apply, what the result format looks like, or whether the operation is safe to run repeatedly.

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 low (33%), and the description barely compensates. It adds 'one customer' to clarify customer_id scope, but provides no meaning for family, date_from, date_to, or limit, leaving the most important query parameters semantically under-specified.

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 names a specific action — running a whitelisted deep-analysis query — and scopes it to one customer, so the core purpose is clear. It does not explicitly differentiate itself from siblings like google_ads_deep_analysis_export or google_ads_insights_query_daily, but the phrase 'deep-analysis query' gives enough distinction for a reasonable agent.

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 guidance about when to use this tool versus alternatives such as google_ads_deep_analysis_export, google_ads_analysis_families_list, or google_ads_insights_query_daily. The word 'whitelisted' hints at a constraint but does not explain prerequisites, authorization, or when another query tool should be preferred.

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