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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that results include the policy reasons and are rendered as a card, which is modest extra value, but it says nothing about scope defaulting, empty-result behavior, or how many accounts are aggregated when neither account nor folder is supplied.

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?

Two short sentences, front-loaded with the resource and scope, with zero filler. The trailing 'Shown as a card' sentence is the weakest part since it describes rendering rather than capability.

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?

The tool is simple (4 optional params, no output schema, no nesting) so the bar is low, and annotations plus a fully documented schema carry most of the load. Still, the description never states what happens with no account/folder (whether it sweeps all accounts) or what the card actually contains, which is the one gap an agent would hit in practice.

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% and two parameters are enums, so the schema fully documents detail, folder, account and language. The description adds no meaning beyond it, leaving this at the baseline for a fully documented schema.

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?

Names a specific resource and qualifier: ads disapproved or limited by Google policy, plus the policy reasons returned. That distinguishes it from generic ad-listing siblings like google_ads_ads without needing to name them, though the description is a noun phrase with no verb to anchor the action.

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 when-to-use guidance, no prerequisites, and no alternative named. An agent must infer that this is the policy-audit view versus google_ads_ads or google_ads_recommendations purely from the resource phrase; 'shown as a card' is presentation, not usage guidance.

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