Creates a new configuration group or appends target items to an existing one, including Pathing targets defined by subdirectory/file.json paths.
新建或向既有配置组追加项目。Pathing 项目的 target 用「子目录/文件名.json」或「文件名」。
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | 配置组名（= 文件名） | |
| type | No | 默认 Pathing | |
| folder | No | Pathing 的公共子目录（可选） | |
| targets | Yes | 项目目标列表 |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden, and it does disclose the important non-obvious trait that existing groups are appended to rather than overwritten. However it says nothing about what happens on duplicate targets, whether writes are persisted/undoable, or the failure mode when a name collides.
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?
Two short sentences, zero filler, with the upsert behavior and the trickiest parameter convention both front-loaded.
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?
There is no output schema and no annotations, so the description is the only behavioral source; it covers the main pitfall (target path format) but omits what the call returns and how the type/folder parameters affect target interpretation.
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%, so the baseline is 3, but the description genuinely adds value by specifying the target path syntax for Pathing ('子目录/文件名.json' or '文件名'), a convention the schema does not state. It leaves the non-Pathing target formats and the folder/type interaction unmentioned.
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 plus non-obvious upsert semantics ('新建或向既有配置组追加项目'), so an agent knows this both creates and appends rather than only creating. It does not explicitly differentiate itself from the sibling bgi_add_group_to_onedragon, which also manipulates group membership.
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?
The create-or-append wording implies when the tool applies, but there are no explicit conditions, prerequisites, or named alternatives. An agent must infer from experience whether to use this versus bgi_add_group_to_onedragon or bgi_run_groups.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.