Upload Ad Image

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

Annotations already declare this is not read-only, so the mutation implied by 'Uploads' is consistent and adds little. The description adds useful context by stating the image is placed in the ad account's image library and returns an image hash for creatives, but it does not disclose side effects such as overwrites, duplicate handling, or access requirements.

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 compact and well-structured, with the core statement first followed by Args and Returns sections. There is no redundant or filler content.

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 moderately parameterized upload tool with no output schema, the description gives enough to call it successfully: required parameters, optional name, and the returned image hash for creatives. The main gap is lack of guidance among upload alternatives, but the core invocation contract is complete.

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 Args section documents ad_account_id, url, and name with functional descriptions, supplementing the schema where ad_account_id and name lack property descriptions. It omits response_format, but the schema fully describes that parameter with an enum, default, and description, so the omission is not harmful.

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: 'Uploads an image to an ad account's image library for use in creatives.' This distinguishes it from sibling tools such as meta_list_ad_images, meta_upload_ad_video, and meta_create_ad_creative by stating exactly what artifact it creates and where it lives.

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 phrase 'for use in creatives' implies the intended use, and the return value mentions when it is needed, but there is no explicit when-to-use guidance or comparison with alternatives like meta_upload_ad_video. An agent must infer from the tool name and sibling list which upload tool to choose.

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