ncloud_list_deny_allow_groups

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

The description only states the basic purpose. The annotation readOnlyHint=true already signals it's a read operation, but the description adds no additional behavioral context such as pagination, sorting, or any limitations. For a listing tool, more transparency about output size or ordering would be beneficial.

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 very concise at five words, but it could be slightly more descriptive without losing efficiency. Nonetheless, it is front-loaded and free of fluff.

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?

Given the existence of sibling tools and parameters for filtering, the description is somewhat complete but lacks details on behavior (e.g., does it return all groups by default?). No output schema is present, so expectations are unclear. Scores adequate but not thorough.

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% with each parameter described. The tool description adds no further meaning beyond the schema, so baseline 3 is appropriate.

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 'List Network ACL Deny-Allow Groups' clearly states the action (List) and the resource (Network ACL Deny-Allow Groups). It effectively distinguishes this tool from sibling tools like ncloud_get_deny_allow_group_detail, ncloud_create_deny_allow_group, etc.

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 usage guidelines are provided. The description does not indicate when to use this tool over alternatives, such as ncloud_get_deny_allow_group_detail for a single group. It also fails to mention that the tool supports filtering via parameters.

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