ncloud_nks_delete_access_entry

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description adds a warning emoji and the 'Destructive' label, reinforcing the safety profile. It also reveals a key behavioral trait: the need to set confirm=true to execute, which is not captured by annotations alone.

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 followed by a brief instruction. It is front-loaded with the purpose and uses a warning emoji for emphasis. Every word earns its place—no fluff or repetition.

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 description explains what the tool does, its destructive nature, and the required confirm flag. For a deletion tool with comprehensive annotations and full schema coverage, this is adequate. It could mention prerequisites or what happens on success, but it is not incomplete given the context.

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?

The schema covers all three parameters with clear descriptions (100% coverage). The description adds value by explicitly stating that confirm must be true to execute, clarifying the role of this boolean parameter. This goes beyond the baseline of 3 for full schema coverage.

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 states 'Delete an IAM access entry from an NKS cluster,' which is a specific verb+resource combination. The name and description clearly distinguish this tool from sibling tools like create, update, get, and list access entries.

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 instructs 'Set confirm=true to execute,' which is a direct usage guideline. However, it does not explicitly mention when to use this tool versus alternatives (e.g., create or update), nor does it provide context for when not to use it. The guidance is minimal but functional.

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