ncloud_add_mongodb_users

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

Annotations already mark destructiveHint: false, indicating a non-destructive mutation. The description adds no further behavioral context, such as whether the operation is idempotent, requires existing instance, or has limits. The annotation provides the key safety info, so the description adds minimal value.

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?

Single sentence with no fluff, but it is very minimal. Could be improved by including key details like that it adds to an existing instance. Acceptable but not exemplary.

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?

Lacks context about prerequisites (e.g., instance must exist), valid authority values (though schema gives examples), or return value. No output schema. For a mutation tool, more description of side effects or constraints would be helpful.

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 having a description. The description does not add additional meaning beyond the schema. Baseline 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) and the target (Cloud DB for MongoDB instance). It distinguishes from sibling tools like list, change, delete by using the verb 'add'. However, it could be more specific by noting 'one or more users'.

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 on when to use this tool vs alternatives. For example, it does not state that this is for adding new users, not modifying existing ones. Siblings like ncloud_change_mongodb_users exist but are not mentioned.

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