Upload Ad Video

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

The description indicates a write operation ('Uploads') which aligns with readOnlyHint=false, but does not disclose any additional behavioral traits such as side effects, file size limits, or overwrite behavior. With minimal annotations, the description adds little beyond the fact that it creates a resource.

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 at two sentences with a clear verb and front-loaded action. However, the parameter list is redundant with the schema and does not add unique value, slightly reducing efficiency.

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?

The description lacks information about the return value or output (e.g., video ID, status). Since there is no output schema, the description should provide this context for a creation tool, but it does not.

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 lists parameters but adds no semantic meaning beyond their names; for example, it does not explain what constitutes a valid file_url or constraints on title. Additionally, the 'response_format' parameter is omitted from the description despite being in the schema. With schema description coverage at 20%, the description fails to compensate for missing parameter details.

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's purpose with a specific verb ('Uploads') and resource ('video to an ad account's video library for use in creatives'), which distinguishes it from sibling tools like meta_upload_ad_image and meta_list_ad_videos.

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 implies the tool should be used to upload videos for creatives but does not provide explicit guidance on when to use it versus alternatives, nor does it mention prerequisites or exclusions.

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