list_mac_groups

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

The annotation readOnlyHint=true already indicates the operation is read-only, and the description's 'list' wording is consistent. The description does not add further behavioral context such as sorting or filtering, but the simplicity of the operation and the presence of an output schema mitigate the need for additional details.

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 a single, concise phrase that directly communicates the tool's function without any unnecessary words or repetition.

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 zero-parameter, read-only list operation with an output schema, the description is adequate to convey purpose. It could explicitly mention that it returns all groups, but the simplicity of the tool makes the current description sufficient.

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 has zero parameters and the input schema is empty, making parameter coverage 100% by definition. With no parameters to describe, the description does not need to provide additional semantics, and the baseline score of 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?

The description '列出 MAC 地址分组' translates to 'List MAC address groups', which clearly identifies the action (list) and the resource (MAC address groups). This distinguishes it from sibling tools like add_mac_group and delete_mac_group, which handle creation and deletion.

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 description does not explicitly state when to use this tool or mention alternatives. However, its purpose as a listing operation is implied by its name and the presence of related add/delete siblings, so an agent can infer that it is used to view existing MAC groups.

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