bilibili_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. It only states the action and the CLI ('sau CLI'), without disclosing side effects, authentication requirements, upload behavior, scheduling, headless modes, failure modes, or return values. This is minimal transparency for a mutating 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?

The description is a single, clear sentence with no redundant words. It is front-loaded and easy to parse. While brief, it earns its place by stating the tool's purpose without fluff.

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 8-parameter upload tool with no annotations, the description is severely incomplete. It provides no context about required arguments, optional settings, scheduling, headless behavior, or prerequisites. Even with an output schema present, the description fails to convey essential usage context for successful invocation.

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 description coverage is 0%, and the description adds no information about any of the 8 parameters. It does not explain the meaning of 'account', 'file', 'title', 'tid', 'desc', 'tags', 'headless', or 'schedule', leaving the agent to rely solely on parameter names and defaults.

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 uses specific verb phrases 'Upload and publish' and names the resource 'a Bilibili video' via 'sau CLI', clearly identifying the tool's action and scope. It distinguishes itself from sibling tools like bilibili_check and other platform uploaders by naming Bilibili and the upload/publish action.

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 usage: when you need to upload/publish a Bilibili video. However, it provides no explicit guidance on when to use this tool versus alternatives (e.g., bilibili_check for status checks) or any exclusions. The context is clear but not fully articulated.

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