meta_ads_ads_enable

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

Despite no annotations, the description discloses key behavioral traits: status change, return values (ad_id and new status), dependency on parent entity status, and reversibility. It could mention potential validation but is sufficient for a simple toggle.

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?

Three sentences, front-loaded with the main action, no redundant words. Every sentence adds value: action, prerequisite, return, reversal.

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 state-toggle tool with no output schema, the description covers all necessary context: purpose, prerequisites, return values, and undo options. It is complete given the tool's complexity.

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 minimal parameter information beyond context (e.g., 'paused ad'). The description does not enhance understanding of account_id or ad_id beyond the 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 the action ('resumes a paused ad'), the mechanism ('setting its status to ACTIVE'), and distinguishes it from siblings like meta_ads_ads_pause. The prerequisite about parent entities adds context.

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?

It provides clear context for when to use (resume paused ad), prerequisites (parent entities must be ACTIVE), and reversal options. However, it does not explicitly exclude cases when the ad is not paused or contrast with other enable tools.

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