list_protocol_groups

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

The description simply states 'list protocol groups', which aligns with the readOnlyHint annotation. It adds no additional behavioral context such as pagination, filtering, or the meaning of protocol groups. However, given the annotation already indicates a safe read operation, the description is not misleading.

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, short phrase that directly states the operation. It is concise but borders on tautological, repeating the tool name without elaboration.

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 parameterless, read-only listing tool with an output schema, the description is minimally adequate. It conveys the basic operation but lacks context about what protocol groups are or how they relate to other tools.

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, so the empty schema covers everything. Per the rubric, the baseline is 4; the description adds no parameter semantics but doesn't need to.

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 Chinese description '列出协议分组' translates to 'list protocol groups', clearly indicating a read-only listing operation. However, it does not differentiate itself from sibling tools like list_custom_protocols or list_port_groups, which also list protocol-related entities.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, typical use cases, or exclusions, leaving the agent without context on when to invoke it.

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