google_ads_get_ad_group_details

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

Annotations are absent, so the description carries the full burden. It states 'Get detailed information', implying a read operation, but does not disclose any behavioral traits like required permissions, rate limits, error handling, or what happens if the ad group is not found. This is minimal transparency.

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 very short (4 lines) and front-loads the purpose. It wastes no words, but the brevity sacrifices important details. Nonetheless, it is concise and to the point.

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?

An output schema exists, so return value details are covered elsewhere. However, given the complexity of the Google Ads API and numerous sibling tools, the description lacks context on what 'detailed information' includes (e.g., name, status, targeting settings). This leaves an agent uncertain whether this tool is appropriate.

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 has 0% description coverage; the description adds notes: 'Customer ID (without hyphens)' and 'Ad group ID', which provide useful formatting guidance beyond the schema titles. This is helpful but still minimal, as it does not explain the expected format or constraints beyond the hyphens note.

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 uses a specific verb+resource ('Get detailed information about an ad group'), clearly indicating the tool's purpose. However, it does not distinguish this tool from siblings like 'google_ads_get_ad_group_performance' or 'google_ads_list_ad_groups', which also deal with ad groups.

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?

No usage guidelines are provided. There is no indication of when to use this tool versus alternatives, such as when detailed information is needed compared to performance metrics or a list of ad groups.

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