ncloud_get_root_password_list

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

The description aligns with the annotation 'readOnlyHint: true', indicating a non-destructive read operation. However, no additional behavioral traits (e.g., pagination, filtering nuances) are disclosed beyond what the annotations provide.

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, clear sentence that is front-loaded and to the point. While concise, it effectively communicates the core purpose without extraneous information.

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 absence of output schema, the description provides minimal context about the return format, pagination behavior, or the criteria for 'can retrieve root password'. For a listing tool with optional parameters, more completeness could improve agent usability.

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 all three parameters described in the input schema. The description does not add any extra meaning or context beyond the existing schema descriptions, so it meets the baseline without enhancing understanding.

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 clearly states the action ('List') and the specific resource ('server instances that can retrieve root password'). It effectively distinguishes from the sibling tool 'ncloud_get_root_password', which likely retrieves the actual password for a single instance.

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 explicit guidance is provided on when to use this tool versus alternatives like 'ncloud_get_root_password' or other listing tools. The usage is implied by the name and description but lacks direct comparison or context.

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