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

Annotations already flag this as destructive, non-readOnly, and openWorld, so the safety profile is declared. The description adds only the '(archive)' nuance and otherwise adds no behavioral context: it doesn't explain that deletion is soft/archival, what happens to associated entities, or the preview-confirm requirement hinted at by confirm_id.

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 short sentence that front-loads the action and resource. It is concise but also under-informative; the parenthetical '(archive)' is the only extra detail.

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 mutation tool with no output schema and half the parameters undocumented, the description is far too sparse. It omits the confirm_id two-step flow, the archive-not-hard-delete semantics, and any prerequisites or consequences, leaving the agent without enough information to call it correctly.

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 the required target_ids parameter has no schema description. The description does not compensate by clarifying the ID format, cardinality, or the meaning of the optional account_id/profile_id. It mentions 'targets' only at the resource level, adding essentially no parameter semantics.

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?

The description states a clear verb and resource: 'Delete (archive) SP negative product targets'. It reveals that deletion is really archiving, which is helpful. It's less specific than it could be — 'negative product targets' in Sponsored Products are the negative targeting entities, and the archive semantics should be made explicit as a non-permanent state rather than packed into parentheses.

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 is given on when to use this tool versus alternatives like ads_delete_sp_negative_keywords, ads_delete_sp_targets, or ads_update_sp_target_state. There is also no mention of the two-step confirmation flow that the confirm_id parameter implies.

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