Upload an image/video asset

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

No annotations provided, so description carries full burden. Discloses return value (asset ID), accepted types, and typical usage. Could improve by specifying behavior when both filePath and url are provided, or error handling (e.g., file not found, size limits).

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?

Single paragraph with logical flow: purpose, accepted types, inputs, usage tips. No redundant sentences; every clause adds value.

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?

For a simple upload tool with no output schema, description adequately explains return and usage. Could mention size limits or authentication requirements for completeness.

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 100% coverage with decent descriptions. Description adds value by listing accepted MIME types (including rejected GIF/WebP) and reiterating that contentType can be inferred. Provides extra context about use in media variables, but could clarify behavior when both filePath and url are present.

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?

Clearly states verb 'Upload' and resource 'image/video asset'. Distinguishes from siblings by explaining that uploaded assets are used in create_video and create_video_from_template.

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 tells when to use this tool versus direct URLs in backgrounds/media variables. Lists accepted and rejected content types, and provides a tip about aspect ratio matching for media variables.

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