ncloud_ncs_get_bucket_lifecycle

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

Annotations already provide readOnlyHint=true, and the description is consistent. It adds valuable behavioral detail beyond annotations by specifying the response when no configuration exists (returns configured=false with empty rule list instead of an error) and listing the rule categories included.

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?

Two sentences with no filler. The first sentence states the purpose and rule types, the second clarifies a key edge-case behavior. Information is front-loaded and every clause earns its place.

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?

For a single-parameter getter with readOnly annotation and no output schema, the description covers the main content (rule types) and a critical edge case. It does not detail the exact response structure, but the description's summary of rule types gives sufficient context for an agent to interpret the result.

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 the bucketName parameter described as 'Name of the bucket to retrieve lifecycle configuration for'. The description adds no additional parameter semantics beyond what the schema already provides, so the baseline of 3 applies.

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 ('Get') and resource ('lifecycle configuration of a Ncloud Storage bucket'), and enumerates the specific rule types (transitions, expiration, noncurrent-version). This distinguishes it from sibling tools like ncloud_ncs_put_bucket_lifecycle or get_bucket_location.

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 a read operation but does not explicitly state when to use this tool versus alternatives (e.g., ncloud_ncs_put_bucket_lifecycle for setting, or ncloud_ncs_delete_bucket_lifecycle for removal). There is no exclusion or alternative guidance, so it relies on inference.

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