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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description adds the specifics an agent actually needs: the exact failure condition (existing destination key), the flag that changes it, and the irreversibility of overwriting. That is genuine added behavioral context rather than a restatement of the hints.

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, zero waste, with the copy-vs-move distinction front-loaded and the failure/overwrite semantics following. Every clause earns its place.

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 mutation tool with no output schema, the description covers the key risk profile: side effects, failure mode, and irreversibility. It omits any hint about the response (e.g., whether the new object's identity is returned) and any cross-bucket constraints, which is a minor gap.

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 coverage is 100%, so the baseline is 3, but the description adds meaning the schema's neutral wording omits: the consequence of overwrite (irreversible replacement), not just its mechanical effect. The other five path/connection parameters are adequately covered by the schema and need no further elaboration.

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?

States a specific verb and resource (copies an object) and immediately distinguishes itself from the sibling move_object by noting the source is left in place. An agent can select this over move_object or write_object without opening any schema.

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?

Gives a clear precondition for use: it fails when the destination key exists unless overwrite is true, which tells the agent when the plain call is unsafe. It does not explicitly name alternatives (e.g., move_object when the source should be removed), so routing guidance is strong but not complete.

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