creatives_create_link_ad

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

No annotations are provided, so the description carries the transparency burden. It discloses the critical media-source constraint and the prerequisite upload workflow, which is valuable. However, it does not mention permissions, reversibility, or what the tool returns after creation, leaving significant behavioral aspects undisclosed.

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 three sentences long, front-loaded with purpose, and every sentence adds useful guidance. There is no filler, redundancy, or unnecessary detail.

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?

With 12 parameters, no schema descriptions, no annotations, and no output schema, the description is too sparse. It addresses the media prerequisite but does not explain the role of most required fields, the broader workflow, or what the operation produces, making it incomplete for such a complex tool.

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 0%, so the description must compensate. It clarifies that image_hash and video_id are mutually exclusive and tied to upload tools, but it leaves the other 10 parameters—including required fields like account_id, page_id, link, and message—completely unexplained. This is only partial semantic value.

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 opens with a specific verb and resource: 'Create a single-image or single-video link ad creative.' This clearly identifies what the tool does and distinguishes it from the sibling tool creatives_create_carousel_ad, which creates a different creative type.

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 the mandatory either/or requirement for image_hash and video_id, and directs the agent to use creatives_upload_image / creatives_upload_video to obtain those values first. It does not explicitly compare against other creative creation tools like creatives_create_carousel_ad, but the usage context is clear enough.

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