Create Automated Ad Rule

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the bar is lower. The description does not add behavioral context beyond the basic purpose, such as whether rules can be paused or what happens on trigger. It is adequate but not enhanced.

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 well-structured with an args list and inline examples, but it could be slightly more concise. However, every sentence adds value, and the examples are helpful.

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?

The description covers all parameters with examples, but it lacks information about the return value or output format, which is not covered by an output schema. Given the tool's complexity (nested objects, 6 params), this gap reduces completeness.

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?

Despite low schema coverage (17%), the description provides detailed explanations and JSON examples for each parameter, including nested objects like evaluation_spec and execution_spec. This adds significant meaning beyond the input schema.

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 'Creates an automated rule for managing ads, ad sets, or campaigns,' which is a specific verb+resource. It distinguishes this tool from sibling tools like meta_create_ad or meta_create_campaign by targeting rules.

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?

The description explains what the rule does but does not explicitly state when to use this tool versus alternatives like meta_create_ad or meta_update_ad. No when-not or alternative tool mentions are provided.

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