set_essence_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 implies a mutation (making a message an essence message) but does not disclose required permissions, reversibility, idempotency, or error behavior. Calling it an 'NapCat 扩展接口' hints at non-standard API support but adds little operational detail.

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 description is short and front-loads the action, which is good. However, the third line is a docstring-style restatement of the already-documented parameter, which is redundant and adds noise without value.

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 one-parameter mutation with no output schema, the description covers the basic 'what' but omits permission requirements, failure modes, and the distinction from sibling essence-message tools. 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% for the single parameter, so the baseline is 3. The description merely restates the schema's own text ('要设为精华的消息 ID'), adding no format, range, or sourcing guidance beyond it.

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 in both Chinese and English ('将指定群消息设为群精华消息', 'set_essence_msg'), so the operation is unambiguous. It does not explicitly distinguish itself from close siblings like delete_essence_msg or get_essence_msg_list, which are the tools an agent could confuse it with.

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 statement of when to use this tool versus alternatives, no prerequisites (e.g. group admin/owner rights), and no note about what happens if the message is already an essence message. The closest thing to guidance is the parenthetical calling it a NapCat extension interface.

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