Download an object from Scaleway Object Storage

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

Even though readOnlyHint and idempotentHint already communicate safety, the description adds important behavioral detail: content is returned as UTF-8 text when possible, otherwise base64, a 5 MB decoded-size cap, and the fail-fast behavior for oversized objects. This goes well beyond annotation values.

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?

Three concise sentences cover the core purpose, return encoding behavior, size limit, and fallback tool. Every sentence earns its place with no filler or redundant restatement.

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?

Even without an output schema, the description tells the agent what to expect: content, included metadata, encoding property, and base64/text handling. It also covers the main failure mode and a concrete workaround, making the tool well-specified for reliable selection and invocation.

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%, so the baseline is 3 and the schema already explains bucket, key, and region clearly. The description does not add extra parameter-level semantics, but it does not need to.

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 action and resource: 'Download a single object's content and metadata.' It unambiguously distinguishes this from sibling tools like scaleway_s3_put_object, scaleway_s3_head_object, and scaleway_s3_generate_presigned_url.

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 explicit when-to-use and when-not-to-use guidance: it explains that larger objects fail fast and directs the agent to 'use scaleway_s3_generate_presigned_url instead.' This is a clear, named alternative with a concrete threshold.

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