Create Ad Creative

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

Annotations already indicate a mutating, non-destructive operation. The description adds the prerequisite of a page_id but does not disclose additional behavioral details such as required scopes, rate limits, or effects on related objects. This is a modest value-add beyond the 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 two sentences, front-loads the purpose, and contains no filler. Every clause contributes meaning.

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 tool with only two parameters, full schema coverage, and existing annotations, the description covers the core functionality and key requirement. It is slightly vague about where page_id lives and doesn't mention return values, but this is acceptable given the tool's simplicity.

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?

The schema already documents both parameters, and the description enhances object_story_spec by specifying supported content types (image, video, carousel) and mentioning a required page_id. This goes beyond the schema's example, though the page_id placement inside the JSON is not explicitly clarified.

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 function with a specific verb ('Create') and resource ('an ad creative'), and elaborates on the object_story_spec JSON field. However, it does not explicitly differentiate from sibling tools like create_ad, so it doesn't fully earn a 5.

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 ad creatives and notes the need for a page_id, but it does not provide explicit guidance on when to choose this tool over alternatives (e.g., create_ad) or mention any exclusions. The context is clear but not comparative.

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