Get Google Ads campaign structure

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=true, covering the safety profile. The description adds the specific components returned (ad groups, keywords, ads, negatives) but does not disclose any additional behavioral details like pagination, error handling, or performance. It is acceptable but minimal given the annotations.

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 sentence with no redundancy, front-loading the action and resource. Every word contributes to the meaning, and it is appropriately sized for the tool's simplicity.

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 there is no output schema and the description is minimal, it lacks parameter clarification and usage context. The description does not explain the role of customer_id or any return format. While annotations cover safety, the description is incomplete for an agent that needs to know how to correctly invoke the tool.

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 has only 50% coverage (customer_id has no description). The tool description does not mention parameters at all, so it fails to compensate for the gap. An agent gets no help understanding the purpose or usage of customer_id, which is a significant omission.

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 verb 'Get' and the resource 'a campaign's ad groups, keywords, ads, and negatives', which is specific and distinguishes it from sibling mutation tools like google_ads_add_keywords or google_ads_remove_keywords. It precisely identifies the scope of the retrieval.

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 provides no guidance on when to use this tool versus alternatives. It does not mention that it is for a specific campaign versus listing all campaigns, nor does it exclude any scenarios. There is no mention of when to prefer it over google_ads_list_campaigns or other retrieval tools.

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