Delete a keyword automation

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

It adds crucial behavioral context beyond the annotations by detailing a multi-step conversational workflow: the first call returns a confirmation requirement, which then necessitates a second, conditional call using the 'confirm' parameter.

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 highly condensed yet comprehensive, front-loading the operational alternative ('Prefer update_keyword...') before detailing the complex, conditional deletion flow.

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?

Given the destructive nature and the multi-step conversational requirement (waiting for confirmation), the description provides maximum possible context without needing an output schema.

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?

While the schema defines 'confirm' as a boolean, the description provides the essential semantic context, explaining that it must only be set to true after a specific DELETE_CONFIRMATION_REQUIRED response is received.

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 explicitly states the purpose (permanently delete a keyword automation) and effectively distinguishes this tool from the sibling update_keyword tool.

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?

It provides explicit guidance on when to use this tool versus the alternative, stating that users should 'prefer update_keyword with isActive false' to pause the keyword.

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