ncloud_delete_mongodb_users

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description adds crucial context that confirm=true is required to execute, preventing accidental deletion. It also explicitly warns 'Destructive'. No contradiction with annotations. It does not elaborate on all consequences (e.g., irreversibility details), but the confirm requirement adds significant transparency.

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?

A single sentence that front-loads the destructive warning and includes the essential execution condition. No filler or redundant words; every part is actionable.

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 simple delete operation, the description is largely adequate: it mentions the destructive nature and confirm requirement. However, it does not describe expected return values or behavior when confirm is false, and lacks any mention of prerequisites (e.g., list users first). With good annotation and schema support, these gaps are minor.

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 descriptions for all parameters including confirm's safety role. The description does not add new meaning beyond the schema—it repeats the confirm requirement. Baseline of 3 is appropriate since the schema already provides adequate parameter clarity.

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 verb 'Delete' and the resource 'users from a Cloud DB for MongoDB instance'. It distinguishes from sibling tools like ncloud_add_mongodb_users and ncloud_change_mongodb_users by indicating deletion specifically. The destructive warning and confirm requirement further clarify intent.

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 implies usage by describing the operation, but it does not explicitly state when to use this tool versus alternatives (e.g., 'Use this to remove users, for adding use ncloud_add_mongodb_users'). No exclusions or prerequisites are provided beyond the confirm flag, so guidance is only implied.

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