Delete Automated Ad Rule

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

The annotation already reports destructiveHint=true, and the description's 'Deletes' is consistent with that. The description adds the object being destroyed—an automated ad rule—but provides no extra behavioral context such as permanence, cascading effects, or authorization requirements.

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 very short, front-loaded with the action, and contains only the necessary parameter explanation. Every sentence contributes to understanding the tool, with no filler or redundancy.

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 simple single-parameter delete operation, the description plus the destructiveHint annotation provide an adequate call contract: what action is performed, which identifier is needed, and whether the operation is destructive. It could note irreversibility or side effects, but the low complexity makes the current level mostly sufficient.

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 0%, but the description includes an Args block clarifying that rule_id is 'Ad rule ID.' This is minimal, yet it gives the agent enough semantic context for the single required parameter.

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 states a specific action and resource: 'Deletes an automated ad rule.' This clearly identifies what the tool does and distinguishes it from delete tools for other object types like meta_delete_ad. It does not explicitly contrast with siblings such as meta_get_ad_rule or meta_create_ad_rule, but the verb and resource are unambiguous.

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?

No guidance is provided about when to use this tool versus alternatives such as meta_delete_ad, meta_get_ad_rule, or meta_list_ad_rules. The description simply states the action, leaving usage context to the agent's inference.

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