delete_lifecycle

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds genuine context beyond them: the [WRITE][risk=medium] tag and especially 'Reversible → prior config', which tells the agent the operation can be undone. The dry_run preview option is also disclosed. Only a small gap remains (no auth/permission requirements).

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?

Front-loaded with the write/risk tags and the action, followed by a compact Args block. Every line earns its place; no redundancy.

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 destructive mutation with annotations present and no output schema, the description covers reversibility, risk level, dry-run preview, and all parameters. It is nearly complete, missing only permission/auth requirements.

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?

With 0% schema description coverage, the description compensates well: bucket_name includes a provenance hint ('from bucket_ls'), dry_run explains the preview behavior, and target explains the default-omission semantics. All three params are covered with meaning beyond the bare schema.

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?

States a specific verb and resource with scope ('Remove all lifecycle rules'), which cleanly distinguishes it from set_lifecycle and bucket_lifecycle_get. It does not explicitly name an alternative sibling, so it stops short of a 5.

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?

There is no explicit when-to-use, when-not-to-use, or alternative routing guidance. The dry_run mention hints at a preview workflow, but the description never contrasts this with set_lifecycle or explains when deletion is appropriate.

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