google_ads_campaigns_get

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

States read-only and lists additional fields returned beyond list. However, no annotations exist, so description carries full burden. Could mention error handling or performance implications, but still sufficiently transparent for a read operation.

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?

Two sentences with no wasted words. Front-loads primary action and distinguishes from sibling. Every sentence adds value.

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 lack of output schema, description specifies exactly what fields are returned (list fields plus extras). Covers purpose, parameters, and usage guidelines completely for this simple read 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?

Schema coverage is 100% with descriptions; the description adds context about parameter relationships (campaign_id from list) and the optional customer_id fallback behavior, enriching understanding beyond schema.

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 it fetches the full detail record for a single campaign by ID, differentiating it from the list tool. It specifies the exact verb and resource, and distinguishes from sibling tool google_ads_campaigns_list.

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?

Explicitly provides when to use ('when you already have a campaign_id') and when not to (use google_ads_campaigns_list for discovery). Also declares read-only, guiding safe invocation.

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