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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation profile is covered. The description adds useful behavior (max 25 per batch, 'Esito verificato per-id' implying per-item partial success), but omits the two-step preview/confirm flow for writes, which is the most important behavioral trait of this tool.

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?

Dense and front-loaded: single vs batch is stated immediately after the purpose, with hard limits (MAX 25) called out. The telegraphic style is efficient, though a couple of clauses read more like notes than prose.

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?

For a destructive mutation with no output schema and 43% schema coverage, the definition covers the core update path but does not surface the mandatory confirm_id/preview step in the description, relying entirely on the schema field comment for a behavior the agent must get right.

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 only 43%, yet the description covers only bid, state, ad_group_id and the items shape, leaving account_id, profile_id and confirm_id to the schema. It also says state is enabled|paused while the schema enum adds 'archived', a minor mismatch that could mislead.

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 verb and resource ('Aggiorna ... ad group Sponsored Display') plus the exact updatable fields (defaultBid, enabled|paused). It is unambiguously distinguishable from ads_update_sd_campaign and ads_update_sp_ad_group by naming the SD ad-group scope.

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 routes the agent between SINGOLA (ad_group_id + bid/state) and BATCH (items, MAX 25) modes, and notes that bid is the primary optimization lever on SD. It does not, however, name an alternative tool or state when-not-to-use, so it falls short of a 5.

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