Launch a Meta ad

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

With readOnlyHint=false already declaring a write operation, the description adds real behavioral value beyond annotations: the ad starts in a paused state and requires preview confirmation before going live. This tells the agent the operation is safe-by-default and has a confirmation gate, though it omits auth requirements and which ad account/campaign the ad attaches to.

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?

Two tight sentences, front-loaded with the core action and immediately followed by the key behavioral caveat (starts paused, needs confirmation). No filler, though the brevity is close to under-specification for a launch tool.

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 low-complexity, zero-parameter tool with no output schema, the description covers the essentials (what it does, paused default, confirmation step). It leaves notable gaps: where the 'your own images or videos' come from when no parameters exist, and which ad account or destination the ad lands in.

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?

Zero parameters, so the baseline is 4. The description mentions 'your own images or videos', which hints at media inputs, but the empty schema with additionalProperties=true means parameter semantics are not really a factor here.

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?

States a specific verb and resource (Launch + Facebook/Instagram ad), and the phrase 'your own images or videos' implicitly distinguishes it from clone-based siblings like launch_cloned_ad. However it does not explicitly name which sibling to prefer over launch_campaign or launch_pmax_campaign, leaving that differentiation to inference.

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 implies usage context (you supply your own media rather than cloning) and notes the workflow (starts paused after preview confirmation), but never states when this tool should be chosen over launch_campaign, launch_pmax_campaign, or launch_cloned_ad. Usage is implied rather than explicit.

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