Get Scaleway bucket object-lock configuration

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

Annotations already indicate a safe read, but the description adds crucial behavioral context: ObjectLockConfigurationNotFoundError means NOT enabled, and there is no disabled state—the config simply does not exist until enabled. This explains an edge case that the schema and annotations do not cover.

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, front-loaded with the core purpose, and every sentence adds value—especially the error-semantics note. No wasted words or repetition of schema fields.

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 read-only configuration check with one required parameter, the description fully covers the essential behavior and error semantics. No output schema is present, but the tool's simplicity and the explanation of the not-enabled condition make it sufficient.

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?

The input schema provides complete descriptions for both bucket and region (100% coverage), so the description need not add parameter details. It does not add meaning beyond the schema, but the schema already does the heavy lifting, justifying the baseline score.

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 tool reads whether Object Lock (WORM protection) is enabled on a bucket, using a specific verb and resource. It also distinguishes from the sibling tool scaleway_s3_enable_object_lock by focusing on the read aspect.

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 clear context for when to use the tool: to check if Object Lock is enabled, with important semantics about the error meaning not-enabled. It does not explicitly name alternatives or exclusions, but the read-vs-write contrast is implied through the sibling tool list and the description's wording.

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