meta_ads_ad_rules_delete

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

No annotations provided, so description carries full burden. It discloses destructive behavior: rule stops firing immediately, evaluation history is purged. Also explains reversibility via rollback_apply but warns about downstream reference breakage due to rule_id change. Sufficient for a delete operation.

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?

Three sentences with no wasted words. Front-loaded with action and return value, then destructive nature, then alternative. Highly concise and well-structured.

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, so description must explain return; it mentions 'Returns a success flag' which is minimal but acceptable. Covers key aspects: action, side effects, reversal option, and alternative. Lacks details like permissions or rate limits, but for a simple delete tool, it's reasonably complete.

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 100% with both parameters fully described. Description adds no additional meaning beyond schema. Baseline 3 assigned as schema adequately covers parameter semantics.

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?

Description clearly states it deletes an Automated Rule, returns a success flag, and is destructive. It distinguishes from sibling tools like meta_ads_ad_rules_update (for disabling) and meta_ads_ad_rules_create. The specific verb 'deletes' and resource 'Automated Rule' provide clear purpose.

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 provides when to use (delete) and when not to use (prefer temporary suspension via update with status=DISABLED). Mentions alternative rollback_apply for reversibility but notes the caveat about rule_id changes. Clear guidance for selecting this tool.

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