video_gen

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

No annotations provided; description includes pricing details ($0.08/call, free tier) and API endpoint, which is helpful but lacks disclosure of output format, speed, limitations, or side effects. Incomplete for a generation tool.

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?

Very concise, two lines. Front-loaded with category and cost. Minor loss of points for omitting expected structured details like result format.

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?

Given the tool's simplicity (1 param, no output schema), the description covers purpose and cost but lacks contextual details like how the video is returned or typical usage. Adequate but could be more informative.

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% description coverage for the single parameter 'prompt' (described as '视频描述'). Description adds no extra semantic value beyond pricing; baseline score of 3 is appropriate.

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 it generates short videos ('短视频生成') and provides pricing. However, it does not differentiate from siblings like 'image_gen' or 'video_analyze', missing explicit resource specificity.

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 guidance on when to use this tool versus alternatives. Does not mention prerequisites, common use cases, or exclusion criteria.

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