google_ads_custom_query

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

No annotations are provided, so the description must disclose behavioral traits. It does not mention whether the query is read-only, potential side effects, error handling, or rate limits. The tool could be used for mutating data via GAQL, but the description is silent on this, posing a risk for agents.

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 concise: a one-sentence purpose, a contextual note with a link, and a brief parameter list. Every sentence adds value with no redundancy or fluff.

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?

Given the complexity of custom GAQL queries and the presence of an output schema, the description adequately introduces the tool's purpose and parameters. It could be enhanced with a note on typical use cases or safety (e.g., read-only constraint), but it is otherwise sufficient for selection.

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?

With 0% schema description coverage, the description adds meaning beyond the schema by explaining that customer_id should be without hyphens, query is a GAQL string, and response_format accepts 'json' or 'markdown'. This helps agents correctly populate parameters.

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 clearly states the tool executes a custom GAQL query, distinguishing it from the many specific Google Ads tools in the sibling list. The verb 'Execute' and resource 'GAQL query' are specific and unambiguous.

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 explicitly targets 'advanced users who want to write their own GAQL queries,' providing a clear use case. It also includes a link to the query builder. However, it does not explicitly state when not to use this tool or mention alternatives, which would be helpful given the many siblings.

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