google_ads_campaigns_diagnose

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

No annotations provided, but description discloses read-only nature ('does not change anything') and outlines output format (ordered list of issues with descriptions and hints). Lists example issues, adding behavioral 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?

Description is concise with multiple sentences each adding value: purpose, output format, read-only note, usage advice. No redundancy. Slightly verbose for a tool but efficient overall.

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 no output schema, description compensates by detailing return type (ordered list), contents (issue names, descriptions, hints), and example issues. Complete for a diagnostic tool with clear use case.

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 already documents both parameters with descriptions (customer_id fallback, campaign_id required). Description adds no additional parameter meaning beyond what's in schema; schema coverage is 100%, so baseline 3 is appropriate.

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?

Clearly states it explains why a campaign is not serving or under-delivering. Specific verb 'diagnose' and resource 'campaign underperformance' distinguish it from sibling tools like performance reports or listing tools.

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 says 'Use this before pulling raw performance reports; it narrows the problem space.' This provides clear guidance on when to use and what alternatives exist.

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