supabase_storage_move

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

The description conveys that the operation mutates state, consistent with the destructiveHint=true annotation. It adds the constraint that the move happens 'within a storage bucket', which matches the single bucket parameter. However, it does not disclose additional behavioral traits like overwrite behavior or that the source is removed, though these are implied by the word 'move'.

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 a single, front-loaded sentence with no fluff or redundancy. It states the operation and resource efficiently, earning a high score for conciseness and structure.

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 simple three-parameter move operation with annotations and no output schema, the description is nearly complete. It defines the main purpose and the within-bucket scope. It could explicitly mention that the source is removed or that the destination must not already exist, but these are reasonably inferred from the word 'move' and the parameter set.

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 descriptions cover 100% of parameters (bucket, fromPath, toPath). The tool description adds no extra semantics about parameter usage, such as path formatting or relative/absolute requirements. With high schema coverage, the baseline of 3 is 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 the operation with specific verbs 'move or rename' and identifies the resource as 'a file within a storage bucket'. This distinguishes it from sibling tools like upload, download, delete, and list, all of which have different purposes. The title 'Move File' reinforces the action.

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 no explicit guidance on when to use this tool versus alternatives. It lacks any mention of prerequisites, such as the destination path being available or the source file existing, and does not contrast with upload/delete combinations or other storage operations. Usage is only implied by the verb itself.

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