ncloud_delete_bucket_lifecycle

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

Annotations already mark destructiveHint=true and idempotentHint=true. The description adds the confirm requirement and clarifies the scope (all rules), providing context beyond annotations.

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 a warning emoji, followed by the guard condition. Extremely concise and front-loaded with critical 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?

Covers the core action and safeguard, but lacks mention of prerequisites (e.g., bucket existence, permissions) or return value. Adequate for a simple destructive tool but could be slightly more complete.

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 input schema fully describes both parameters (bucketName, confirm) with accurate descriptions. The description only repeats 'Set confirm=true to execute', adding no new meaning.

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?

Clearly states it deletes all lifecycle configuration rules from a Ncloud Storage bucket. Uses specific verb 'delete' and resource, and distinguishes from sibling tools like get and put.

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?

Provides the requirement to set confirm=true to execute and notes it's destructive, but does not explicitly state when to use vs alternatives (e.g., put_bucket_lifecycle for specific rule removal).

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