Upload Ad Image

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds that the tool returns an image hash for use in creatives, but does not disclose rate limits, authorization requirements, or behavior on duplicate uploads. With annotations present, the description provides minimal extra context.

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 with a clear purpose statement, bulleted args, and return value. It front-loads the key action. The 'Args:' section is somewhat redundant with the schema but still efficient, with no wasted words.

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 no output schema, the description includes the return value. It explains the tool's purpose and basic parameters, but misses the response_format parameter and does not address authentication or potential errors. For a simple upload tool, it is mostly adequate but has gaps.

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 description adds meaning for ad_account_id and name, which lack schema descriptions, and clarifies that the return value is an image hash. However, it omits the response_format parameter entirely, despite the schema defining it with an enum and default. Schema coverage is 50%, and the description partially compensates but is incomplete.

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 uploads an image to an ad account's image library for use in creatives, using a specific verb and resource. It distinguishes from sibling tools like meta_upload_ad_video and meta_list_ad_images by focusing on image upload.

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 provides no guidance on when to use this tool versus alternatives, such as when an image already exists or when to use list_ad_images. No prerequisites or exclusions are mentioned.

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