ncloud_add_mysql_users

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

The description only states 'Add users', implying a write operation. Beyond the annotation (destructiveHint: false), no behavioral traits are disclosed, such as whether existing users are affected, password policies, or network implications. Given sparse annotations, more context is needed.

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 sentence that is front-loaded and concise. No extraneous information is present, though additional context could be added without sacrificing brevity.

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?

The tool involves an array of user objects and has no output schema. The description lacks details on return values, error conditions, or behavioral effects, making it insufficient for an agent to fully understand the tool's behavior.

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 clear descriptions for each parameter (instance number, user list with fields). The description adds no additional meaning beyond summarizing the action, so a baseline score of 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 clearly states the action 'Add users to a Cloud DB for MySQL instance', identifying the verb and resource. However, it does not differentiate from sibling tools like ncloud_change_mysql_users or ncloud_delete_mysql_users, which share similar context.

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 guidance is provided on when to use this tool versus alternatives. The sibling list includes related tools (e.g., change, delete users), but the description does not mention prerequisites or when not to use this tool.

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