Create Ad Creative

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

Annotations indicate a write operation (readOnlyHint=false), consistent with 'creates'. The description adds that the output is the creative ID but lacks details on side effects, rate limits, or required page permissions. It provides adequate but not comprehensive behavioral context beyond annotations.

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, using a clear 'Args:' list structure front-loaded with purpose. Each sentence serves a purpose, though it could be slightly more compact. No waste.

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 moderate complexity (9 parameters, no output schema), the description covers the primary purpose and param details but lacks guidance on dependencies (e.g., creative ID needed for meta_create_ad) and does not clarify fallback logic when object_story_id is omitted. It is adequate but not fully comprehensive.

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 33% (only page_id and object_story_id described). The description lists all parameters with inline descriptions, adding meaning (e.g., object_story_id format, parameter types). However, it omits the 'response_format' parameter included in the schema, which is a gap.

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 'Creates an ad creative from an existing Facebook Page post', specifying the verb (creates), resource (ad creative), and source (existing post). It distinguishes from siblings like meta_create_ad (creates an ad, not a creative) and meta_create_adset.

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 implies usage for creating an ad creative from a post but does not explicitly state when to use this tool vs alternatives (e.g., meta_create_ad which might also create a creative inlined). No when-not-to-use or context about prerequisites like page permissions.

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