delete_campaign_folder

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

Annotations provide destructiveHint=true and idempotentHint=true. Description adds that deletion is permanent and irreversible, and importantly that campaigns are not deleted but become unfiled. This extra context about side effects goes 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?

Very concise: three sentences plus Args/Returns sections. Front-loaded with purpose. No unnecessary words. Structured clearly.

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?

Covers purpose, behavior, parameter guidance, and return format. Lacks mention of error cases or prerequisites (e.g., permissions). For a simple delete tool, it is fairly complete, especially with output schema existing.

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%. Description explains folder_id well ('Campaign folder ID to delete. Obtain from list_campaign_folders'), but completely ignores the optional account parameter. Partially compensates for the required param but misses half.

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 'Delete a campaign folder permanently' with specific verb and resource. It distinguishes itself from other delete tools by clarifying that campaigns inside are not deleted. This differentiates it from sibling delete tools like delete_campaign.

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?

Provides clear context for when to use (delete folder permanently) and important behavior (campaigns become unfiled). Mentions using list_campaign_folders to get IDs. However, it does not explicitly state when not to use or compare with alternatives like delete_campaign.

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