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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the agent knows this is a destructive write. The description adds no behavioral context beyond that — it does not mention the preview/confirm two-step flow (only hinted at by the schema's confirm_id), any limits, or what effect negative targets have.

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 terse sentences, front-loaded with the action and then the payload contract. No filler, every clause carries information.

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, no-output-schema mutation tool the description covers purpose and payload, but omits the confirmation workflow, validation constraints, and error behavior. The destructiveHint annotation carries the safety profile, so this is adequate but not complete.

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?

The schema leaves the required `targets` array with no item schema, and the description fills that gap by specifying each element's fields: campaign_id, ad_group_id, and asin (or raw expression). This is genuine added meaning for the one required parameter, though the optional account_id/confirm_id semantics are covered 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?

"Create SP negative product targets" gives a clear verb (create) and specific resource (SP negative product targets), which distinguishes it from the sibling ads_create_sp_negative_keywords and ads_create_sp_product_targets. It is a clear statement of purpose, though it does not explicitly name the alternatives it differs from.

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?

The description gives no when-to-use context, no when-not-to-use, and no mention of alternatives such as ads_create_sp_negative_keywords (keyword-level negatives) or the corresponding delete/list tools. It only explains the payload shape, leaving the agent to infer when this tool is appropriate.

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