add_mac_groupCreate a MAC address group on an iKuai router by providing a group name, optional comment, and MAC list for organizing devices by hardware address.
添加 MAC 地址分组
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| comment | No | ||
| mac_list | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does 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 discloses nothing: not whether an existing group name is overwritten or rejected, not what permissions are needed, not whether the change is reversible. It simply restates the tool title.
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 a single short phrase with no wasted words, but this is under-specification rather than genuine conciseness for a mutation tool with three undocumented parameters. Nothing is front-loaded because nothing substantive is present.
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?
An output schema exists, so return values need not be explained. However, for a write operation with zero annotations and zero parameter documentation, the description omits the behavioral and input-format context an agent needs to invoke it correctly.
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 0% for all three parameters. The description adds no meaning for 'name', 'comment', or the critical 'mac_list' field, whose expected format (comma-separated, one per line, ranges?) is completely undocumented in both schema and description.
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 plus resource ('添加' / add, 'MAC 地址分组' / MAC address group), so an agent can tell what object is being created. It does not explicitly distinguish itself from the sibling tools list_mac_groups or delete_mac_group, but the add/create semantics are unambiguous.
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 tool versus list_mac_groups, delete_mac_group, or the sibling add_mac_speed_limit / add_mac_access_control tools. No prerequisites, ordering, or exclusion conditions are stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.