Delete Do Not Reach list

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description builds on this by stating the concrete consequence 'Suppression stops' and requiring confirm=true after user confirmation. This adds useful behavioral context beyond the annotations, clarifying that the operation is irreversible and requires explicit confirmation. No contradiction with annotations.

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?

The description is three short, direct sentences with no filler. It front-loads the primary action, then states the confirm condition and the effect. Every sentence contributes to understanding, and there is no redundant content.

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 simple delete operation with destructiveHint and readOnlyHint already provided, the description covers the key points: action, confirm requirement, and effect. However, it does not explicitly state that it deletes a specific list (do_not_reach_list_id), nor does it describe the behavior when confirm is false, the response format, or any prerequisite steps. Given the 3-parameter schema and no output schema, a bit more detail would improve completeness.

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 33% (account_id is described). The description explains the confirm parameter's purpose ('confirm=true after the user named it'), which adds meaning beyond the schema. However, do_not_reach_list_id is not described, and while its purpose is inferable from the tool name, the description does not fully compensate for the low schema coverage. It provides some value but leaves gaps.

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 clearly states the verb 'Delete' and the resource 'account DNR list', and adds the effect 'Suppression stops.' This distinguishes it from sibling tools like x_ads_create_dnr or x_ads_list_dnr. However, it is slightly ambiguous whether it deletes a single list or the entire account-level list, though the do_not_reach_list_id parameter clarifies the intended scope.

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 only guidance is 'confirm=true after the user named it', which is a condition for the confirm parameter, not guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or direct references to sibling tools such as x_ads_create_dnr or x_ads_list_dnr. An agent would have to infer usage from the tool name alone.

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