kuaishou_upload_video

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

No annotations are provided, so the description must carry the full burden of behavioral transparency. It only states 'upload and publish' and 'via sau CLI', offering no details on side effects, authentication requirements, or operational risks. The agent knows it is a write/publish operation but lacks deeper behavioral context.

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 a single, direct sentence with no filler, which is concise. However, it is so brief that it sacrifices essential detail, making it minimally useful despite its efficiency.

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 a tool with 7 parameters, 3 required, and a complex operation like uploading and publishing to a social platform, the one-sentence description is severely incomplete. It provides no guidance on parameter semantics, success/failure behavior, or return value, and the output schema does not compensate for the lack of explanatory context.

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 zero description coverage (0%), and the description adds no parameter-specific meaning. It does not explain what 'account', 'file', 'title', 'desc', 'tags', 'headless', or 'schedule' mean or how they should be used, leaving the agent with only parameter names to infer from.

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 action ('Upload and publish'), the target resource ('a Kuaishou video'), and the mechanism ('via sau CLI'). This is specific and distinct from sibling tools like douyin_upload_video or bilibili_upload_video by naming the platform.

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 implies use for Kuaishou video uploads, which differentiates it from other platform upload tools, but it does not explicitly state when to use it versus alternatives or provide exclusions. The context from sibling names offers indirect guidance only.

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