meta_ads_ads_create

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

With no annotations, the description discloses mutation, non-reversibility, and suggests recording before-state with mureo_state_action_log_append. It also reveals the default initial status and return value. However, it does not mention error behavior or permission requirements, leaving some gaps.

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 sentences cover purpose, return value, mutation warning, default status, and creative prerequisite. It is front-loaded with the primary action and efficient with no redundant fluff.

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?

Given the 5-parameter create operation, no output schema, and no annotations, the description covers the key aspects: what it does, prerequisites, return value, and mutation implications. It lacks some operational details like failure handling, but is complete enough for most use cases.

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%, so parameters are already well-documented. The description adds context about the creative prerequisite and default status, but mostly reinforces schema details rather than introducing new semantic meaning.

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 the tool creates a new ad inside an existing ad set and binds it to a pre-existing creative, returning the new ad id. This specific verb+resource+scope distinguishes it from sibling creation tools like meta_ads_campaigns_create and meta_ads_creatives_create.

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 explicitly tells the user to first create a creative using meta_ads_creatives_create or sibling constructors, establishing a clear prerequisite and alternative. It also notes the default PAUSED status, giving contextual guidance on when this tool is appropriate.

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