Create Video

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

With no annotations, the description carries the full behavioral burden and does disclose two non-obvious traits: files are uploaded to the creator's own third-party Bunny Stream library, and the listing does not accept orders until encoding completes (an asynchronous gate). It still omits permissions/auth requirements and failure handling, which keeps it from a 5.

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 tightly written sentences, no filler. The core purpose is front-loaded and the second sentence adds the storage/encoding behavior that an agent needs before calling.

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 an 8-parameter mutation tool with no annotations and no output schema, the description covers the storage destination and the encoding gate but not the return value — notably it never mentions that this likely produces an upload/encoding job the agent must poll via get_upload_job, nor the wallet prerequisites implied by payoutWalletIds.

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 100%, so the schema already explains all 8 parameters (price format, preview clip being a separate file, payoutWalletIds defaults, verifyPayer credit cost). The description adds only the high-level note that previewClip is optional, so baseline 3 applies.

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?

States a specific verb and resource (sell/create a video listing) and clarifies the source of the file ('from this computer'), which separates it from URL-based siblings like create_link. It does not explicitly name which sibling to use instead of this one (create_gallery, create_series, add_episodes), so it stops short of full differentiation.

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?

Usage is implied rather than stated: 'Sell a video from this computer' tells the agent this is for locally-stored single videos, but there is no explicit when-to-use/when-not, no mention of prerequisites such as having a payout wallet configured, and no routing to create_gallery/create_series for multi-item cases.

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