delete_campaign_structure

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

Discloses deletion order and dry run behavior. No annotations provided, so description carries burden. Missing details on auth requirements, rate limits, or side effects (e.g., impact on associated assets).

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?

Front-loaded with main purpose. Single paragraph with structured arg descriptions. No redundant sentences. Efficiently uses 5 lines for action and 4 parameters.

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?

No output schema; description does not state return value (e.g., list of deleted items or success message). Does not mention prerequisites like campaign status or account/permissions. Partial coverage of key details.

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%, so description compensates well. Explains account_id, campaign_ids_json (JSON array or null), delete_all_active (targets all if true and no IDs), confirm (true=delete, false=dry run). Adds logical context beyond schema types.

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?

Clear verb 'delete', specific resource 'campaign structure (ads -> adsets -> campaigns)'. Distinguishes from sibling tools like update_campaign or duplicate_campaign by explicitly naming the hierarchical deletion in correct order.

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?

Explains two modes: specific campaign IDs or delete_all_active. Provides dry run guidance via confirm parameter. Does not compare with alternative actions like deactivating campaigns, but gives sufficient context for typical usage.

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