meta_ads_videos_upload

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

Discloses mutation effect ('asset is persisted') and asynchronous processing delay. No annotations present, so description carries full burden. Could mention potential error conditions like URL accessibility or file format issues, but current coverage is good.

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 plus a sibling reference. Front-loaded with core purpose and output. Every sentence is necessary and informative.

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 covers all essential aspects: purpose, input constraints, output, async behavior, and alternative. No output schema exists, but description adequately explains return value and usage in creative-construction tools.

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 coverage is 100%, baseline 3. Description adds meaning beyond schema: account_id fallback, URL requirements (public HTTPS, formats, max size), title purpose. Adds value without redundancy.

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 URL to a Meta Ads account and returns a video_id. It explicitly mentions the alternative for local file uploads (meta_ads_videos_upload_file), distinguishing it from its sibling.

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 states when to use this tool (for videos hosted at public URLs) and when not (use meta_ads_videos_upload_file for local files). Provides clear context for selection.

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