gads_query

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It only says 'execute a raw query' and gives an example. It fails to disclose whether this is read-only, any rate limits, response format, or potential errors. The example implies a SELECT query but does not guarantee the tool is non-mutating or explain its behavior beyond execution.

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 two sentences plus a representative example. It is front-loaded with the action and purpose, contains no filler, and every sentence earns its place. The example is succinct and illustrative.

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 single-parameter tool with no output schema, the description covers the essential purpose and when to use it. It does not describe the output format or error handling, which would be valuable, but the example and clear scope make it reasonably complete for its simplicity.

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?

The schema describes the param simply as 'A valid GAQL query string'. The tool description adds a full example query, demonstrating the expected syntax and structure, which provides meaningful enrichment beyond the schema's minimal definition.

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's function with a specific verb ('Execute') and resource ('raw Google Ads Query Language (GAQL) query'). It distinguishes itself from sibling tools by noting it is for 'custom queries not covered by other tools' and provides a concrete example.

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 states when to use it ('Use for custom queries not covered by other tools'). It does not name specific alternatives but clearly implies that other tools cover predefined queries. This is clear contextual guidance, though it lacks explicit 'when not to use' phrasing.

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