meta_ads_ads_enable

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

With no annotations, the description carries the full burden of disclosure. It clearly explains the state change to ACTIVE, the prerequisite condition, the returned values (ad_id and new status), and that the operation is reversible. It doesn't mention auth or error behavior, but this is adequate for a simple state-change tool.

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 two sentences long, front-loaded with the primary action, and contains no filler or redundant information. Every sentence contributes useful context.

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 two-parameter tool with no output schema, the description covers purpose, prerequisites, return values, and reversibility. It is complete enough for an agent to understand when and how to use the tool.

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 clear descriptions for both ad_id and account_id. The description doesn't add parameter semantics beyond the schema, but it doesn't need to because the schema already documents each parameter well.

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's purpose: it resumes a paused ad by setting its status to ACTIVE. It specifies the resource (ad) and distinguishes itself from pause/enable operations on parent ad sets or campaigns.

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?

Provides clear context by noting the parent ad set and campaign must also be ACTIVE for the ad to serve. It also names reversal paths (rollback_apply or meta_ads_ads_pause), but doesn't explicitly contrast with meta_ads_ad_sets_enable or meta_ads_campaigns_enable.

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