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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that: no granularity, default date behavior, or note on which of the 17 filters actually affect the trend series.

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?

A single front-loaded sentence with no filler, which is structurally fine. But brevity here reflects under-specification rather than disciplined conciseness for a 17-parameter tool.

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?

An output schema exists, so return values need not be explained, but the input side is a black box: 17 optional parameters with no documentation anywhere. For a tool of this complexity the description is far too thin.

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?

All 17 parameters have 0% schema description coverage and the description mentions none of them. Terms like date_from/date_to, range_preset, days, sort_by, limit, and campaign_name are left entirely unexplained, so the agent must guess at their meaning and interaction.

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?

States a specific resource (Google Ads spend/clicks/conversion trends) and scope ('this account'), which is enough to distinguish it from a summary or campaign-list tool. However it never explicitly contrasts itself with close siblings like google_ads_get_summary or google_ads_get_fatigue, leaving the agent to infer the difference.

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?

No guidance on when to choose trends over google_ads_get_summary, google_ads_get_campaigns, or google_ads_get_fatigue, and no mention of prerequisites or typical scenarios. The agent gets a topic but no routing logic.

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