upload_ad_image

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

No annotations are provided, so the description carries full behavioral burden. It doesn't state whether the URL is fetched asynchronously, format/size limits, whether the image persists or is deduplicated, or what permissions the ad_account_id requires. 'By public URL' hints at a fetch requirement but nothing more is disclosed.

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?

A single tight sentence with no waste, front-loading the action and mechanism. Appropriately sized for the operation described.

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?

Output schema exists so return values needn't be explained, but the description is still thin for a mutation/upload tool with no annotations and 0% schema coverage. Missing: auth context for ad_account_id, URL fetch semantics, and validation limits, leaving real gaps for correct invocation.

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_url is a public URL (adding meaning beyond the bare 'Image Url' title) but says nothing about ad_account_id — what it's for, whether it's required, or how it affects the upload.

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?

States a specific verb+resource ('Upload an image') and clarifies the mechanism ('by public URL') and intended use ('to use in creatives'). This distinguishes it from sibling 'upload_ad_video' by resource type, though it doesn't explicitly contrast with 'create_ad_creative'.

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?

Implied usage is derivable from 'to use in creatives' — the image is a prerequisite asset for creative creation. However, no explicit when-to-use/when-not guidance, and the relationship to siblings like create_ad_creative (must you upload before creating a creative?) is left to inference.

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