meta_ads_page_posts_boost

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

Discloses that the tool is mutating and not automatically reversible, and suggests using mureo_state_action_log_append for rollback. No annotations provided, so description carries the full burden and does well.

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 concise, with each sentence adding value: purpose, return value, mutation warning, prerequisite, and alternative. No redundant 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 no annotations and no output schema, the description covers the tool's function, constraints, prerequisites, alternatives, and return value. Minor gaps exist (e.g., eligibility checks), but overall it is thorough.

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 description coverage is 100%, so baseline is 3. The description does not add significant new meaning beyond what the schema already provides for each parameter.

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 it boosts an existing Facebook Page post by creating a paid ad using that post as creative. It distinguishes itself from meta_ads_ads_create, which is used for creating a new creative ad.

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?

Explicitly provides when to use (boost existing post) and when not (for new-creative ads use meta_ads_ads_create). Also mentions prerequisites like the ad_set_id must already exist with budget and targeting configured.

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