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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is known. The description adds the payload item shape but omits the two-step confirm_id workflow, which is a meaningful behavioral trait only relayed via the schema.

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 compact sentences, front-loaded with the action, and every clause carries information (the item structure is not repeatable elsewhere). No filler.

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 write tool with no output schema, the description covers the array payload but leaves the confirmation workflow and idempotency/scope expectations unstated. Annotations and schema cover safety and confirm_id, so the omissions are noticeable but not crippling.

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 required 'targets' array carries no schema description, and the description fills that gap by specifying the per-element shape: { campaign_id, ad_group_id, asin (or raw expression) }. This meaningfully compensates for the 67% coverage gap, though account_id and confirm_id are left to 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+resource: 'Create SP negative product targets.' This is clearly distinguishable from ads_create_sp_negative_keywords (keyword vs product) and ads_create_sp_product_targets (positive vs negative) by resource noun, even though no sibling is named 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?

No guidance on when to use this versus the positive-target or negative-keyword siblings, and no mention of prerequisites even though the schema implies a preview-then-confirm workflow. The agent must infer all routing and precondition rules.

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