set_qq_profile

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 does not say whether unspecified fields are preserved or cleared, whether it requires a logged-in session, whether changes are reversible, or what the response contains. For a mutation tool with zero annotation coverage this is a substantial gap.

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?

Front-loads the core purpose in the first clause with the NapCat action name; the rest is param echoing that duplicates the schema. Reasonably tight, though the repeated :param lines add little beyond the structured fields.

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?

A profile-setting mutation tool with no annotations and no output schema leaves behavioral questions unanswered, and the 100% schema coverage offsets the missing param detail. It is adequate for a simple setter but not complete for safe 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 the schema already documents all three parameters, and the description merely restates them verbatim (nickname, personal_note, sex with the same enum-style codes). Baseline 3 applies since the schema does the heavy lifting and no syntax or format value is added.

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 (当前登录 QQ 账号的个人资料), making the operation clear. It does not explicitly distinguish itself from close siblings like set_self_longnick, set_qq_avatar, or set_friend_remark, but the target (the logged-in account's own profile) is well-scoped.

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?

Provides no when-to-use guidance, prerequisites, or alternatives. With siblings such as set_qq_avatar and set_self_longnick covering adjacent profile fields, the agent gets no help deciding which tool to reach for. Usage is only weakly implied by the description.

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