delete_campaign_folder

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

Annotations (destructiveHint, idempotentHint) are supplemented by description stating permanence, non-destruction of campaigns, authentication, concurrency limit, and dry-run respect. Adds significant behavioral context beyond 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?

Well-structured with a one-liner followed by bullet points for key behaviors and parameters. Slightly verbose but all sentences add value. Could be shorter but still clear.

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?

With an output schema, the description covers behavior, parameters, side effects, and references related tools. Provides complete guidance for a destructive action.

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 0%, but the description fully explains both parameters: folder_id (source from list_campaign_folders) and account (optional, with account naming convention and reference to list_accounts). Adds meaning beyond schema titles.

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 action ('Delete a campaign folder permanently'), specifies the resource ('campaign folder'), and notes permanence. It distinguishes from siblings like delete_campaign or update_campaign_folder by focusing on folder deletion and its behavior.

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?

Explicitly states the irreversible nature and that campaigns become unfiled, providing context for when to use. References list_campaign_folders to obtain folder IDs. Does not explicitly list when not to use but adequately guides usage.

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