get_group_system_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, and it does not say whether the call is read-only, whether fetching consumes/acknowledges the messages, whether results are paginated or bounded, or what shape the response takes. For a queue-like notification feed those behaviors matter.

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?

A single, front-loaded sentence with the resource first and the parenthetical examples immediately after; the OneBot 11 API reference is appended compactly. No padding, though it is a little thin for the amount of behavior left unstated.

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 no-parameter read tool with no output schema, the description covers what kind of records come back, which is the minimum an agent needs. It omits the safety profile, result bounding/pagination, and any hint about how the returned system messages relate to the approval siblings, leaving clear gaps.

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?

The tool takes zero parameters and the schema declares an empty object, so there is no parameter semantics for the description to add. Baseline 4 applies.

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?

States a specific verb and resource (获取群系统消息列表) and enumerates the content types covered (pending join approvals, group-invite notices), which lets an agent tell it apart from generic history tools like get_group_msg_history. It does not name any sibling explicitly, so it stops short of full differentiation.

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: the mention of '待审批的入群申请' suggests this is the read step before acting via set_group_add_request, but there is no explicit when-to-use statement, no exclusion, and no disambiguation against the closely related sibling get_recent_notices_and_requests.

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