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

Annotations already declare destructiveHint=true and openWorldHint=true; the description adds non-derivable context: ARCHIVED is irreversible and forbidden, batch is capped at 25, and outcomes are reported per-id rather than as a single success flag. It omits the preview/confirm_id two-phase write behavior, which only surfaces in the schema, keeping it short of a 5.

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 with purpose, then constraints, then mode syntax — dense and waste-free. The telegraphic all-caps style ('SINGOLA', 'BATCH', 'PER-ID') is efficient but requires a small inference step, so it is not maximally clear.

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 6-parameter tool with no output schema, the description covers scope, limits, exclusions and granularity of results. The missing pieces are the confirm_id confirmation flow and the effect on already-ARCHIVED or non-existent ads, both of which an agent would want before writing.

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% and all parameters are optional, so mode selection is genuinely ambiguous from the schema alone; the description resolves it by pairing ad_id+state (single) vs items (batch, max 25). It says nothing about profile_id, and account_id/confirm_id meaning lives only in the 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?

States a specific verb pair (pause/reactivate ENABLED/PAUSED) and an exact resource (SP product ad = single sponsored ASIN/SKU inside an ad group), and explicitly scopes out campaign/ad group state changes, which is precisely how it differs from siblings ads_update_sp_campaign and ads_update_sp_ad_group.

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?

Gives the prerequisite for identifiers (ad_id from ads_list_sp_product_ads), an explicit exclusion (ARCHIVED not permitted), and the two invocation modes (single: ad_id+state; batch: items array, max 25). An agent knows both when to call it and how to shape the call.

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