get_essence_msg_list

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

With no annotations, the description carries the full behavioral burden and delivers little: it never states whether admin/bot permissions are required, whether results are paginated or capped, or what the response contains. Only the 'NapCat 扩展接口' note hints at the underlying implementation.

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?

It is short and front-loads the purpose. The trailing ':param group_id: 目标群号' is redundant with the schema, but the overall size is appropriate for a one-parameter read tool.

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?

With no output schema and no annotations, the description should at minimum sketch the return value or access constraints; it does neither. For an agent deciding whether it can call this and what to expect back, the definition is incomplete.

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 required parameter, so the baseline is 3. The description merely repeats the schema text ('目标群号') without adding format or constraint detail (e.g., how to obtain a group_id, whether it must be one the account has joined).

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+resource ('获取指定 QQ 群的精华消息列表') and identifies the backing interface (NapCat extension: get_essence_msg_list). It is clearly a read of a group's pinned/essence messages, though it does not explicitly contrast itself with the sibling mutators set_essence_msg and delete_essence_msg.

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 the related siblings set_essence_msg or delete_essence_msg, nor any prerequisite such as needing to be a group admin. Usage is only inferable from the verb '获取'.

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