Get Scaleway bucket lifecycle rules

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, indicating a safe read operation. The description adds the specific error condition 'NoSuchLifecycleConfiguration' when no rules exist, which is valuable behavioral context beyond the annotations. No contradictions.

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 extremely concise with two sentences, each adding value: the first states the action, the second warns about the error case. No superfluous text, and the key information is front-loaded.

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 lacks an output schema, so the description should compensate by explaining the structure of lifecycle rules (e.g., an array of rules with filters, transitions). It only says 'Read a bucket's lifecycle rules' without describing the return format, leaving the agent uninformed about what to expect. This is a significant gap for a simple tool.

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 description coverage is 100%, with both parameters ('bucket', 'region') adequately described in the input schema. The description does not add any additional meaning or usage details beyond what the schema provides, so it meets the baseline of 3.

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 action: 'Read a bucket's lifecycle rules.' It also specifies the error condition for absent rules, which differentiates it from sibling tools like put/delete lifecycle. The verb+resource combination is specific and unambiguous.

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 usage for reading lifecycle rules, but it does not provide explicit guidance on when to use this tool versus other S3 read tools (e.g., get_bucket_policy, get_bucket_tagging). No alternatives or exclusions are mentioned, leaving the agent without clear differentiation among sibling S3 read tools.

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