gads_campaign_performance

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

Discloses default filters and sorting but does not mention behavioral traits like pagination, rate limits, or error handling. No annotations are provided, so the description bears full burden but covers only defaults.

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 short and front-loaded with the purpose, then lists metrics and defaults. Every sentence earns its place without redundancy.

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 tool with 6 parameters and no output schema, the description covers core functionality and defaults adequately. However, it lacks details on return format and potential limitations, leaving some gaps in completeness.

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 high (83%), so the description adds minimal value beyond schema. It repeats defaults already in schema but does not explain metric semantics in more depth.

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 provides 'Campaign-level performance' and lists specific metrics (impressions, clicks, CTR, avg CPC, cost, conversions, conv value, CPA, ROAS), differentiating it from sibling tools like ad_group_performance or keyword_performance.

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 mentions default settings (last 28 days, enabled campaigns, sorted by cost desc) but does not explicitly guide when to use this tool vs alternatives like gads_conversions_by_campaign. Usage is implied but lacks exclusion criteria.

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