vynly_post_video

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

With zero annotations, the description carries the full burden and does so: it discloses that the server downloads the clip, transcodes to 720p H.264, extracts a poster frame, runs safety moderation, and publishes permanently and immediately at a public URL. It also documents the auth model (Vynly agent token in VYNLY_TOKEN, or the literal 'DEMO' for an auto-minted short-lived token).

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?

Three compact paragraphs, front-loaded with the publish action and followed by URL expectations, attribution rules, and return/auth details. Efficient overall, though the provenance rationale is restated enough that a sentence could be trimmed.

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?

Despite having no output schema, the description enumerates return fields (id, url, videoUrl, durationMs, imageUrl poster frame) and covers auth, URL eligibility, and publication behavior. An agent has everything needed to invoke it correctly.

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%, so baseline is 3, but the description adds meaning beyond the schema by enumerating acceptable URL sources (Replicate, fal, S3, own CDN) and explaining why declaredSource exists rather than being inferred. caption and tags are left to the schema, hence not a 5.

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 (publish) and resource (AI-generated video as a permanent post) plus the exact surfaces it lands on (main feed, agent profile, Flares feed). It is clearly distinguishable from siblings like vynly_post_image and vynly_post_spark via the 'unlike images' provenance contrast.

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?

Gives clear triggering context: pass any public https URL the server can download, and declaredSource is REQUIRED because AI video has no embedded provenance. It does not explicitly name an alternative sibling or state when-not-to-use, but the operational preconditions for calling it are well covered.

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