meta_ads_videos_upload

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

With no annotations provided, the description fully discloses that the tool is mutating (persists the asset) and that Meta performs asynchronous processing after upload, which may take a few minutes. This gives the agent a clear understanding of the tool's behavior and side effects.

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 the core purpose, and each sentence adds distinct value: function, return value, mutating behavior, async processing, and sibling distinction. No superfluous 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 the tool's simplicity (3 params, no output schema), the description covers all necessary aspects: what it does, how it works, what it returns, and when to use alternatives. The asynchronous processing note is especially helpful for planning subsequent steps.

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 input schema already has 100% description coverage for all three parameters. The description adds valuable context beyond the schema, noting that the title is 'Used for library organization; not shown in ads,' and mentions supported formats (MP4, MOV) and max size (4 GB), which are not present in the schema.

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 a video from a public HTTPS URL to a Meta Ads account and returns a video_id for use in creative-construction tools. It specifically distinguishes itself from the sibling tool meta_ads_videos_upload_file, which handles local file 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?

The description provides explicit guidance on when to use this tool vs. the alternative: 'For uploads from local files use meta_ads_videos_upload_file.' It also notes the asynchronous processing and potential delay before the video can be attached to ads, helping set expectations.

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