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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the mutation risk is covered structurally. The description adds the batch cap (MAX 25) and 'Esito verificato per-id' partial-failure semantics, but omits the confirm_id preview/confirm workflow and what ARCHIVED irreversibly does.

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?

Front-loaded verb+resource, then two labelled clauses (SINGOLA/BATCH) with the constraint inline. No wasted words and easy to scan.

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?

Covers the core operation and batch limits, but for a destructive mutation with no output schema it omits the confirmation flow and account/profile scoping an agent needs to invoke it safely. Adequate but with clear gaps.

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 50%; the description explains the items=[{target_id, state}] shape and the single-mode pairing, which reinforces the key params. It adds nothing for account_id, confirm_id or profile_id, leaving those to the schema, so it sits at the baseline.

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 (Aggiorna) plus resource (stato di product target Sponsored Brands) and enumerates the exact states ENABLED|PAUSED|ARCHIVED. The 'SB' scope distinguishes it from siblings like ads_update_sp_target_state and ads_update_sb_target_bid.

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?

Clearly documents the two invocation modes (SINGOLA: target_id + state; BATCH: items=[...], MAX 25), which is useful selection context. However it never states when to prefer this tool over sibling update tools or the prerequisites/authorization needed, leaving usage implicit.

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