s3_copy_object

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

The description explicitly discloses the destructive behavior: 'Overwrites the destination if it exists.' It also notes 'dangerous guard mode,' adding a risk signal. With no annotations, this is valuable behavioral transparency, though it omits permissions or error handling.

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 short, front-loaded sentences deliver the core purpose, a key behavioral warning, and a usage constraint with zero wasted words.

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 copy tool with no output schema, the description covers the operation type, scope constraint, overwrite behavior, and a safety gate. It misses edge cases like cross-region behavior or source retention, but these are largely implied by 'copy' and the schema's region parameter.

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 schema already documents all parameters. The description does not add any parameter-specific meaning beyond the schema's own descriptions, making baseline 3 appropriate.

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 'Server-side copy of an S3 object within the same provider,' with a specific verb and resource. This distinguishes it from s3_move_object, s3_upload_object, and s3_download_object sibling tools.

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 phrase 'Reserved for dangerous guard mode' implies a restricted context, and 'copy' implies it is not for moving (which s3_move_object handles). However, there is no explicit when-to-use/when-not-to-use guidance or named alternatives.

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