s3_put_bucket_lifecycle

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

The annotations already mark this as destructive and idempotent. The description adds valuable behavioral detail: passing rules: [] clears the entire lifecycle configuration, and B2 does not support Transition/storage-class rules. This helps an agent avoid invalid or unintended calls.

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 three short, information-dense sentences with no filler. The primary action is front-loaded, followed by clearing behavior and supported/unsupported rule types.

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 schema already documents all parameters and the annotations cover safety behavior, the description adds the essential B2-specific context. The only minor gap is that it does not explicitly state that setting non-empty rules replaces any existing lifecycle configuration, but this is largely implied by the 'set' and 'clear' semantics.

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%, so the baseline is 3. The description adds meaningful semantics beyond the schema by explaining that rules: [] clears the configuration and by enumerating the supported lifecycle actions. The confirm parameter is not described in the description, but the schema already covers it.

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 clear verb and resource: 'Set S3 lifecycle rules on a B2 bucket.' It also names the supported rule types and the key B2-specific limitation around Transition/storage-class rules, which distinguishes this tool from general S3 mutation tools.

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 gives clear context: this is the tool for lifecycle configuration on a B2 bucket and it clarifies what rule types are supported. It does not explicitly name sibling tools as alternatives or state when not to use this tool, but the scope is specific enough that the intended use case is clear.

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