send_private_forward_msg

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 is a mutation tool, yet nothing is said about permissions, rate limits, whether the message is reversible, or what the return value looks like. The node format example is useful but is structural, not behavioral.

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 purpose is front-loaded and the example is valuable, but the trailing ':param' lines merely restate the schema descriptions verbatim, adding length without new meaning. The OneBot 11 action-name reference is only marginally useful.

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 tool whose only real complexity is building the nested node array, the inline example makes it callable. However, with no annotations and no output schema, the description should at least hint at success/failure behavior or the result shape, and it does not.

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 coverage is 100%, so the baseline would be 3. However, the description goes beyond the schema by supplying a concrete node format example ('[{type: node, data: {name, uin, content}}]'), which is genuinely needed to construct the 'messages' array that the schema leaves as an untyped items:{} list. This adds real construction value.

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 ('向指定好友发送合并转发消息' – send a merged forward message to a specified friend), which inherently distinguishes it from send_group_forward_msg (group) and send_private_msg (single message). It does not explicitly name those siblings, but the scope 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?

There is no when-to-use or when-not-to-use guidance, and no alternatives are named. An agent must infer that this is the tool for multi-node merged forwards to friends versus send_private_msg for single messages, but the description never states that.

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