gads_run_gaql

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

No annotations are provided, so the description carries full burden. It only labels the tool as an 'escape hatch' and includes a link to documentation, but does not disclose behavioral traits like error handling, rate limits, or potential complexity. This is insufficient for a raw query tool.

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?

Extremely concise: two sentences plus a link. Every part is essential. Front-loaded with 'Escape hatch' and purpose, immediately followed by usage guidance and a reference to external documentation.

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 no output schema and no annotations, the description should provide more behavioral and result context. It lacks details on query constraints, output format, or error handling. The brief description is insufficient for an unannotated tool of this nature.

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?

Input schema covers both parameters (query and customer_id) with descriptions, achieving 100% schema coverage. The description adds no additional semantic information beyond what the schema provides, so baseline score of 3 is appropriate.

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?

Explicitly states it runs any raw GAQL query against Google Ads, with clear verb and resource. Differentiates from sibling tools by calling it an 'escape hatch' for when preset tools don't cover the report shape, making its unique purpose clear.

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?

Provides explicit context: 'Use when preset tools don't cover the report shape you need.' This tells when to use it, but does not specify when not to or list alternative tools by name. The sibling list implies alternatives, but the description could be more explicit.

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