upload_video

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

No annotations are provided, so the description carries full burden. It discloses that it is a WRITE operation, returns `{id, title}`, and notes potential limitations for `file_path` (blocked on Windows/sandboxed hosts). This goes beyond basic function and adds useful 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?

Two sentences, front-loaded with 'WRITE:', and no wasted words. Every sentence provides essential information without redundancy.

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?

No output schema exists, so description adequately explains the return value (`{id, title}`). It covers main usage patterns and a key limitation. Lacks error scenarios or detailed response fields, but is reasonably complete for a video 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 has 6 params with 67% coverage; description adds significant value by explaining why `file_url` is recommended over `file_path` and mentions the return structure. This clarifies the intent of key parameters beyond their schema definitions.

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?

Description clearly states 'WRITE: Upload a video to an ad account.' It specifies the action, resource, and context, and distinguishes itself from siblings by focusing on video file upload. The return value is also mentioned.

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 excellent guidance on when to use `file_url` vs `file_path` and explains why `file_path` may be unsuitable. However, it does not compare this tool to sibling tools like `create_ad_creative` or `upload_image`, leaving the when-to-use-this-tool-vs-alternatives partially incomplete.

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