arvan_vod_create_video

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

Annotations provide no behavioral info (readOnlyHint, destructiveHint, idempotentHint all false). Description does not disclose side effects, permissions, or return behavior. Minimal transparency.

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, front-loaded with purpose, no wasted words. Efficient and clear.

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?

Lacks output schema and does not describe return value. No mention of error cases or constraints on channel_id. Partial coverage for field object but not comprehensive.

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 0% description coverage. Description adds meaning to 'fields' by listing typical entries (title, description, file_id, optional convert_mode, watermark_id). No info on channel_id parameter.

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 'Create a video in a channel' and provides typical fields like title, description, file_id. It is specific to video creation among many VOD create tools.

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?

No explicit guidance on when to use this tool versus alternatives like arvan_vod_create_audio or arvan_vod_create_subtitle. The description relies solely on the tool name for distinction.

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