google_ads_network_performance_report

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

Discloses return shape, filtering of Display/YouTube/Discover, rounding of metrics, and read-only nature. No annotations provided, so description carries full burden; lacks details on pagination or data freshness but is otherwise transparent.

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?

Concise yet comprehensive: starts with purpose, details output structure, filters, rounding, read-only flag, and usage guidance. No fluff.

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?

With 3 params, no output schema, and a report tool, the description fully covers functionality, output format, filtering, rounding, and sibling differentiation. All necessary context for an agent is provided.

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%, baseline 3. Description adds value for period parameter with usage advice (e.g., short windows for recent changes). Customer_id and campaign_id are well explained in schema; description does not repeat but context is sufficient.

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 identifies the tool as reporting Google Ads performance split by ad network (Google Search vs. Search Partners), with a specific verb 'Report' and resource. It distinguishes from sibling tools by stating the split and filtering out other networks.

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 on when to use this tool: 'Use this to decide whether to toggle Search Partners. For overall campaign totals use google_ads_performance_report; for per-ad breakdowns use google_ads_ad_performance_report.' Also provides context for the period parameter.

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