xhs_login

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. It transparently describes the browser window, QR code, waiting for scanning, and automatic saving of login state, giving a clear picture of the interactive process. It does not cover timeouts or failure scenarios, but the core behavior is well disclosed.

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 sentence that front-loads the action ('登录小红书') and efficiently explains the entire process in a concise, structured way. Every phrase contributes meaning with no redundancy.

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 zero-parameter interactive login tool, the description covers the main flow and persistence of login state. However, it does not specify the return value or whether the function blocks until scanning, which could be gaps given the absence of an output schema. Still, it's sufficiently complete for the tool's simplicity.

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 tool has zero parameters, and schema coverage is 100% (vacuously). According to the baseline rule for 0 parameters, a score of 4 is appropriate; the description does not need to explain any parameters since there are none.

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: logging into Xiaohongshu by opening a browser, displaying a QR code, waiting for scanning, and saving login state. It explicitly distinguishes from siblings like xhs_check_login and xhs_logout, making the purpose unmistakable.

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 initial login and notes that login state is persisted for future use, but it does not explicitly compare with xhs_check_login or explain when not to use. There is no explicit when/when-not guidance, only implied context from the login flow.

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