google_ads_campaigns_get

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

With no annotations provided, the description states it is read-only and specifies the extra fields returned. However, it does not mention error behavior (e.g., if campaign_id is invalid) or rate limiting. Still, it provides meaningful transparency beyond the schema.

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 concise: four short sentences that cover purpose, return fields, read-only nature, and usage guidance. No unnecessary words.

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?

Despite lacking an output schema, the description lists the additional fields returned. It provides clear when-to-use and when-not-to-use guidance. For a single-campaign retrieval tool, it is complete and leaves no critical gaps.

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%, so baseline is 3. The description adds context about campaign_id (e.g., 'as returned by campaigns.list') but does not provide additional semantic details beyond what the schema already explains. No significant value added for parameters.

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?

Description clearly states the verb ('Fetches') and the resource ('full detail record for a single campaign by ID'). It distinguishes itself from its sibling 'google_ads_campaigns_list' by specifying it is for when you already have a campaign_id, and lists additional fields returned.

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?

Explicit guidance: 'Use this when you already have a campaign_id; for discovery use google_ads_campaigns_list.' Also notes it is read-only, indicating safe usage without side effects.

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