sandbox_file_rename

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

With no annotations provided, the description must disclose behavioral traits. It states the operation is renaming/moving, but does not mention that the operation is destructive (overwrites existing file at newPath), whether authentication is needed, or if the sandbox must be active. This is a significant omission for a mutation tool.

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 concise sentence, front-loaded with the core action. It is appropriately sized for a simple tool. No 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?

Given the tool has no output schema, no annotations, and 3 required parameters, the description should provide more context about return values, error conditions, and side effects. It is incomplete for an agent to use safely.

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?

The input schema has 100% coverage, describing all three parameters with clear descriptions. The tool description does not add additional meaning beyond the schema, but the schema itself is adequate. Baseline 3 is appropriate as schema provides sufficient semantic information.

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 uses specific verbs 'rename' and 'move' targeting a file or directory in a sandbox. It clearly states the resource (file/directory) and the operation (rename/move). However, it does not differentiate from sibling tools like sandbox_file_write or sandbox_file_remove, though the action is distinct enough.

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 no guidance on when to use this tool versus alternatives like sandbox_file_mkdir or sandbox_file_remove. It does not mention prerequisites (e.g., file must exist) or limitations (e.g., cannot move across sandboxes). Sibling tools perform other file operations but no contrast is given.

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