ncloud_put_bucket_lifecycle

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

Annotations are empty, so the description bears full burden. It indicates a mutating operation ('Set lifecycle rules') and mentions dryRun for preview, but does not disclose side effects such as overwriting existing rules, permission requirements, or idempotency. The description is minimal and leaves behavioral implications implicit.

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 two sentences—front-loaded with the purpose and immediately providing a dryRun tip. Every sentence earns its place with zero waste or unnecessary 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 tool has a complex input with nested rule objects, but no output schema. The description does not explain rule structure, replacement semantics, or return behavior. While the schema covers fields, the description lacks context like whether the operation replaces existing rules or prerequisites, leaving gaps for a mutating tool with this complexity.

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% per context signals, so baseline is 3. The description mentions storage classes (ONEZONE_IA, DEEP_ARCHIVE) and dryRun, but these are already documented in the schema. No additional semantic value is added beyond summarizing key features already present.

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 a specific action (Set lifecycle configuration rules) with a clear resource (Ncloud Storage bucket) and highlights supported features (storage class transitions and object expiration). It is not a tautology and distinguishes itself by covering the main capabilities.

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 provides a usage tip for dryRun=true ('Use dryRun=true to preview the configuration') but does not contrast with sibling tools like get/delete lifecycle or specify when to use this vs alternatives. It implies usage by stating it sets rules, but lacks explicit exclusions or alternative guidance.

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