Copy an object within or across Scaleway Object Storage buckets

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

Annotations already convey readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description adds value by explaining that the copy is server-side, which clarifies no local data transfer occurs, and explicitly constrains source/destination to the same region. It does not contradict the annotations.

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 two sentences, front-loaded with the core operation, and contains no filler. It efficiently states what the tool does, the key benefit, and the main constraint.

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 rich schema and annotations, the description is adequately complete for tool selection and invocation. It covers purpose, mechanism, and the critical same-region requirement. It could mention overwrite behavior or permissions, but these are not essential given the existing metadata.

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 all parameters already described in the input schema. The description reinforces the same-region constraint and destination semantics but does not add substantial meaning beyond what the schema already provides.

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 identifies the specific action: a server-side copy of one object to a new bucket/key. It distinguishes this from sibling tools like scaleway_s3_put_object, scaleway_s3_get_object, and scaleway_s3_delete_object by stating the operation happens without downloading and re-uploading.

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 usage context: use this for server-side copying within the same region. It does not explicitly name alternative tools or state when not to use it, but the same-region constraint and 'without downloading and re-uploading' help the agent choose appropriately.

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