meta_ads_images_upload_file

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

Description explicitly notes the tool is mutating ('Mutating — the asset is persisted'), which compensates for the absence of annotations. It also mentions the return value (image_hash). Could add more about permissions or rate limits, but current detail is adequate.

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?

Three concise sentences with no fluff. The most critical information (purpose, return value, usage guidance) is front-loaded and clearly communicated.

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 the tool simplicity (3 parameters, no output schema), the description covers purpose, parameters, return value, mutation semantics, and when to use alternative tools. No notable 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?

Input schema has 100% coverage with detailed descriptions for all three parameters (account_id, file_path, name). The description does not add significant new information beyond the schema, so baseline 3 is appropriate.

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 from a local file path to the Meta Ads account library, returns the image_hash, and distinguishes it from the sibling tool meta_ads_creatives_upload_image which handles public-URL uploads.

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?

Explicitly provides when to use (image on local disk) and when not to use (public-URL uploads), naming the alternative tool. This aids correct tool selection.

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