meta_ads_ad_rules_delete

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

With no annotations, the description carries the full burden of behavioral disclosure. It fully discloses the destructive nature, immediate stoppage, purging of evaluation history, non-reversibility, and the new rule_id on re-creation. This is thorough and transparent.

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 concise and well-structured, starting with the primary action, then the success flag, followed by important alerts and alternatives. Every sentence provides necessary information without unnecessary fluff, making it easy to scan and act upon.

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 complex destructive delete operation with no annotations and no output schema, this description covers all essential aspects: immediate effect, data purge, reversibility, rollback mechanism, and alternative for suspension. It is sufficiently complete for an agent to invoke it correctly.

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 100%, and the schema already explains rule_id and account_id formats, requiredness, and fallback behavior. The description adds context about rule_id's role in rollback (re-creating assigns a new ID), but does not add parameter-specific syntax or meaning beyond the schema, so the baseline score of 3 is appropriate.

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 'Deletes an Automated Rule' with a specific verb and resource, and it distinguishes itself from sibling tools by explicitly noting that temporary suspension should use meta_ads_ad_rules_update instead. The phrase 'Returns a success flag' also clarifies the return 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?

Explicit usage guidance is provided: 'For temporary suspension prefer meta_ads_ad_rules_update with status=DISABLED.' It also advises recording before-state for rollback and warns about downstream references, giving clear context on when this tool is appropriate versus alternatives.

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