Send an official announcement to a specified QQ group, including title and content, directly from the NapCat server. Resolve the need to notify group members by creating and publishing the notice instantly.
Send group announcement
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | Announcement title | |
| content | Yes | Announcement content | |
| group_id | Yes | Group ID |
Changes observed during successful MCP inspections.
v0.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Send group announcement' and does not mention permissions, side effects, return data, CSRF/auth requirements, or failure behavior. This is effectively no behavioral information.
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 extremely short, but this is under-specification rather than effective conciseness. It front-loads nothing useful and provides no structured or scoped information.
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?
The schema fully covers parameters and the tool is simple, but the description omits usage context, behavioral details, and any distinction from closely related sibling tools. An agent would still lack enough information to understand what invoking this tool involves.
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 schema descriptions cover 100% of the three parameters with basic meaning ('Announcement title', 'Announcement content', 'Group ID'). The description adds nothing beyond the schema, so the baseline of 3 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?
The description 'Send group announcement' is essentially a restatement of the tool name 'send_group_notice'. It identifies a verb and resource, but adds no detail to distinguish it from siblings like send_group_msg or get_group_announcement_list.
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?
No guidance is given about when to use this tool versus alternatives such as send_group_msg or get_group_announcement_list. There are no conditions, exclusions, or prerequisites stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.