set_self_longnick

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

No annotations are provided, so the description carries the full behavioral burden. It mentions the operation targets the 'currently logged-in QQ', but omits whether this overwrites an existing signature, what permissions are required, rate limits, or what the return value looks like.

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 sentence is front-loaded and concise, but the trailing ':param long_nick: 个性签名内容' duplicates the schema verbatim and does not earn its place in the description.

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 simple one-parameter setter with no output schema, the description covers the core action and the target account. However, with no annotations, it should provide more behavioral context such as success/failure conditions or authentication requirements.

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 the single required parameter 'long_nick'. The description merely repeats the schema's parameter description ('个性签名内容'), adding no extra syntax, format, or length constraints.

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 states a specific verb and resource: '设置当前登录 QQ 的个性签名' (set the currently logged-in QQ's personalized signature). It is clear what the tool does, but it does not differentiate itself from sibling tools like set_qq_profile or set_qq_avatar, which could also affect 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 tool versus alternatives such as set_qq_profile or set_qq_avatar. The description only states what it does, leaving the agent to infer context and any prerequisites.

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