create_video_task

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

With no annotations provided, the description carries full burden for behavioral disclosure. It reveals the task is paid and asynchronous but omits details such as whether it is destructive, idempotent, or any rate limits/authentication nuances. The description is insufficient for safe agent invocation.

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?

The description is very short (one sentence) but contains a typo ('APIAny') that reduces clarity. It is front-loaded with purpose, but the awkward phrasing and missing structure (e.g., no bullet points or organization) make it less effective.

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 11-parameter tool with no output schema and no annotations, the description is far too minimal. It does not explain return values, error handling, or the nature of the async task (e.g., how to poll status). Essential context for a paid API is missing.

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?

The schema has 64% description coverage, so baseline is 3. The description adds value by clarifying that 'confirm_paid_request' must be set to true for paid requests, which is not explained in the schema (only shows default false). This extra context raises the score to 4.

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 verb 'Create' and the resource 'video task', and it specifies that it is an async video generation task. However, it does not explicitly distinguish itself from the sibling tool 'create_image_task', though the resource name implies the difference. The typo 'APIAny' slightly detracts but does not obscure meaning.

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?

The description provides a prerequisite (APIANY_API_KEY and confirm_paid_request=true) but does not guide when to use this tool versus alternatives like 'create_image_task' or 'estimate_cost'. There is no when-not-to-use or explicit context for choosing this tool.

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