switch_qq_account

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

With no annotations, the description carries the full burden and does a reasonable job: it discloses that the default config and OneBot 11 port config are auto-updated, and that restart_immediately=True kills the old account process and restarts with the new one. It omits failure modes (target uin never logged in, port never ready) and any permission/auth prerequisites.

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 core behavior is front-loaded in the first two clauses before the parameter list, and nothing is padded. The :param block duplicates schema text, which is mild redundancy but keeps it scannable.

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 purpose, side effects, restart semantics, and the meaning of all three parameters. What remains missing is error/edge-case behavior and prerequisites, but an agent has enough to invoke it 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 100%, so all three parameters are already documented in the schema, and the description's :param lines are near-verbatim restatements. No additional meaning (formats, constraints, interactions) is added, so the baseline 3 applies.

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?

States a specific verb and resource (switch the currently active QQ account) and scopes it with 'hot switch between multiple already logged-in QQ numbers', which implicitly separates it from login_new_qq_by_qrcode. It never names a sibling outright, but the operation is unambiguous.

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 parenthetical 'supports hot-switching between already logged-in QQ numbers' implies the precondition for use, and the restart_immediately behavior signals the tradeoff involved. However, it never says when NOT to use it (e.g. use login_new_qq_by_qrcode for a fresh account) or points to list_qq_accounts to enumerate valid targets.

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