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 structurally. The description adds nothing beyond that: it does not say the deletion is permanent/irreversible, whether it cascades, or that a two-step confirmation (evidenced by the confirm_id param) is required.

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?

It is a single four-word phrase with no wasted sentences, but this is under-specification rather than effective conciseness — the brevity carries no front-loaded operational 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 only 50% parameter documentation, the description should carry far more load. Instead it delegates all meaning to a sparse schema and the annotations, leaving the confirmation flow and ID sourcing unexplained.

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?

With 50% schema description coverage, the description is expected to compensate, but it adds zero parameter meaning. keyword_ids (the required array) has no description, profile_id is undocumented, and the two-step confirm_id/account_id semantics are only discoverable by reading the Italian schema text.

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 is essentially the title/name restated: 'Delete SP negative keywords' adds no scope, no effect, and no differentiation from the many sibling delete tools (ads_delete_sp_negative_targets, ads_delete_sp_targets, ads_delete_sp_campaign). An agent learns nothing about what 'SP negative keywords' means operationally beyond the name.

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 when-to-use guidance, no exclusions, and no pointer to alternatives such as ads_list_sp_negative_keywords (to find IDs) or the sibling delete variants. The agent must infer the workflow entirely from the name.

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