set_qq_profile

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

No annotations are supplied, so the description carries the full burden. It discloses that the target is the current logged-in account, but for a mutation tool it says nothing about permissions, persistence, reversibility, or what happens to fields left unspecified. The 'NapCat 扩展接口' note is a provenance tag rather than behavioral context.

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?

Short and front-loaded with the purpose, which is good, but the three :param lines duplicate the input schema exactly and consume most of the description without earning their place.

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 three-optional-parameter mutation with no annotations and no output schema, the description covers the target scope but leaves behavior and sibling selection unexplained. It is minimally adequate rather than complete.

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% and the description merely repeats the schema text verbatim (:param nickname, personal_note, sex with the same wording). It adds no format, constraint, or interaction detail beyond the structured fields, so 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+resource (修改...个人资料) and scopes it precisely to the currently logged-in QQ account, which separates it from group/friend profile tools. It does not, however, disambiguate from close siblings like set_self_longnick or set_qq_avatar, both of which also touch self-profile fields.

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?

There is no guidance on when to use this versus set_self_longnick (long nickname) or set_qq_avatar, nor any note about prerequisites such as being logged in. The only usage-relevant fact is the scope in the first clause.

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