xiaohongshu_upload_video

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only states the high-level action. It fails to disclose important traits such as authentication requirements, side effects of publishing, headless mode behavior, or scheduling semantics.

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 and is front-loaded, containing no redundant filler. However, it is terse to the point of under-specification for a 7-parameter tool, which limits its usefulness but still maintains structural 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?

For a tool with 7 parameters, 3 required, and an output schema, the one-sentence description is grossly incomplete. It omits parameter semantics, usage context, side effects, and any behavioral detail, making it inadequate for an agent to invoke correctly.

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 compensates with zero parameter information. It does not clarify the meaning of required fields (account, file, title) or optional fields (desc, tags, headless, schedule), leaving the agent without any semantics beyond raw parameter names.

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 tool's function with a specific verb ('Upload and publish') and resource ('Xiaohongshu video'), which distinguishes it from sibling check tools (e.g., xiaohongshu_check) and upload tools for other platforms (e.g., douyin_upload_video, bilibili_upload_video).

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 is provided on when to use this tool versus alternatives. The description does not mention exclusions, prerequisites, or any comparison with other Xiaohongshu or upload tools, leaving the agent without context for tool selection.

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