google_ads_cpc_detect_trend

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

With no annotations, the description fully discloses behavioral traits: it is read-only, explains the trend direction logic (thresholds for rising/falling), data exclusions (zero-click days), and output structure including optional fields. It also describes insights generation for surges and anomalies.

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 well-structured and front-loaded with the core purpose, but slightly verbose in detailing the return object. Every sentence earns its place, but minor trimming could enhance conciseness.

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 the complexity (3 parameters, no output schema), the description is complete. It details the full return structure, trend logic, edge cases (insufficient data, zero-click exclusions), and insights. The parameter descriptions also provide sufficient context.

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 the schema already documents parameters. However, the description adds value by explaining the customer_id fallback mechanism and providing contextual advice for period selection, going beyond what the schema offers.

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 explicitly states the verb ('Detect'), resource ('CPC trends in a Google Ads campaign'), and method ('using daily segmentation and linear regression'). It also distinguishes from sibling tools by naming alternatives for device and auction-share investigation.

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 provides explicit when-to-use advice (CPC trend detection) and direct alternatives ('For device or auction-share investigation use google_ads_device_analyze or google_ads_auction_insights_analyze'). Parameter descriptions also offer usage guidance for period selection.

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