upload_video_asset

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

With no annotations, the description discloses file validation, size limit, and that video enters processing post-upload. While it lacks details on auth requirements or error handling, it provides adequate behavioral 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 and well-structured: a clear summary paragraph followed by a bulleted arg list. Every sentence adds value without repetition.

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 complexity and lack of output schema, the description covers validation, size limits, processing steps, and return value. It also references poll_video_processing, making it contextually complete for an upload tool.

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%, but the description lists all parameters with examples (e.g., 'act_123456789' for account_id) and notes optionality, adding meaning beyond 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 local video file to a Meta ad account, specifying validation, size limit (<1GB), and return of meta_video_id. It differentiates from sibling tools like upload_video_resumable and poll_video_processing.

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?

Provides context for when to use this tool (files <1GB) and mentions poll_video_processing for checking readiness. It implies that upload_video_resumable is for larger files, offering clear usage guidance.

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