get_essence_msg_list

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

No annotations are provided, so the description carries the full burden. It implies a read operation via 获取, but says nothing about return shape, whether the list is paginated or capped, ordering, or required permissions for the group.

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 core purpose stated first. The trailing ':param group_id:' docstring artifact is slightly redundant clutter but the whole entry stays compact.

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 read getter with no output schema, the description is minimally adequate. It does not describe what the returned list contains or how large it may be, which is the main remaining gap.

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% with a single required group_id already documented as 目标群号 in the schema. The description merely repeats that same meaning, adding no format or constraint detail beyond the schema.

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: 获取 (get) the 精华消息列表 (essence/pinned message list) for a specified QQ group. This clearly separates it from the write-side siblings set_essence_msg and delete_essence_msg, though it never explicitly names them.

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?

Usage is only implied by the tool name and read semantics; the description gives no when-to-use, no prerequisites, and no mention of the sibling mutation tools. An agent can infer it is the read counterpart, but nothing is stated explicitly.

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