meta_ads_page_posts_boost

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

The description discloses that the tool is mutating (creates an ad), reversible (via rollback_apply, which pauses the boosting ad), and that the original post stays live. Since no annotations are provided, the description carries full burden and covers essential behaviors. It could mention rate limits or permissions but is adequate.

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 four concise sentences, each with a clear purpose: main action, return/reversibility, prerequisite, and alternative. No fluff, front-loaded with key information.

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 tool's complexity, the description covers prerequisites, alternatives, and return value (ad_id). No output schema exists, but the return is simple. It provides sufficient context for an agent to select and invoke correctly.

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%, and the description adds context: account_id optional with fallback, name auto-generated if omitted, and ad_set_id prerequisite. This adds meaning 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 tool's action (boosts an existing Facebook Page post), the resource (existing post), and the return value (new ad_id). It also distinguishes from sibling tools by mentioning meta_ads_ads_create for new-creative ads.

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 states when to use this tool (only attaches post as creative to an existing ad set) and when not to (for new-creative ads, use meta_ads_ads_create). It also provides prerequisite (ad_set_id must exist with budget/targeting) and reversibility via rollback_apply.

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