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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description does add one real behavioral fact beyond annotations — '(archive)' signals a soft/reversible delete rather than a hard purge. However, it omits the confirmation workflow implied by confirm_id, idempotency, and the effect on live campaigns, which matters for a destructive write.

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 zero wasted words; the resource and operation lead. It is terse to the point of under-specification, but as a conciseness measure it is efficient.

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 4-parameter mutation with no output schema, the description should explain the preview/confirm requirement and expected outcome; it does neither, and the required target_ids parameter is undocumented in both description and schema. Only the destructive annotation carries context.

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 description coverage is only 50%: account_id and confirm_id are documented, but profile_id and the required target_ids have no description anywhere. The description adds no parameter-level meaning at all, so it fails to compensate for the coverage gap on the one required field.

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+resource ('Delete SP negative product targets') with the clarifying parenthetical '(archive)'. An agent can distinguish it from ads_delete_sp_targets (positive targets) and ads_delete_sp_negative_keywords, though the description never names those siblings explicitly.

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?

There is no when-to-use guidance, no prerequisite (e.g. needing a preview first), and no mention of alternatives such as ads_delete_sp_targets. The schema exposes a confirm_id preview/confirm flow, but the description never tells the agent that deletion is a two-step operation.

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