switch_qq_account

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

No annotations are provided, so the description carries the full burden. It discloses key behaviors: automatic updates to default and OneBot 11 port configs, stopping the old account process, and restarting with the new account when restart_immediately=True. The wait_seconds parameter and its default are also explained. However, it doesn't mention potential side effects like downtime during restart or permission requirements.

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 front-loaded with the core action, followed by behavioral details and parameter descriptions. Every sentence adds value without redundancy, and the structure is clear and efficient.

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 mutation tool with no annotations and no output schema, the description covers the essential behavior: what it does, how it updates configs, and restart options. It could be more complete by mentioning the expected outcome (e.g., success confirmation) or error conditions like invalid uin, but it is largely sufficient for correct 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 100%, so all parameters are already documented in the schema. The description repeats the same information about uin, restart_immediately, and wait_seconds without adding new semantic details like valid formats or edge cases. Baseline 3 is appropriate when the schema fully covers parameters.

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 specific verb and resource: '切换当前使用的 QQ 账号' and explains it supports hot-switching between multiple logged-in QQ accounts. It distinguishes itself from login_new_qq_by_qrcode and other account tools by focusing on switching between already logged-in accounts.

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 multiple accounts are logged in and provides context about automatic configuration updates and restart behavior. However, it does not explicitly state when to use this versus login_new_qq_by_qrcode or list_qq_accounts, nor does it mention prerequisites like requiring at least one other account already logged in.

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