rename_project

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

With no annotations, the description carries the full burden. It discloses that overwrite=True replaces an existing project, which is a key destructive behavior. However, it omits other details such as whether the operation is reversible, what happens if old_name doesn't exist, or any permission requirements. This is average transparency 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 front-loaded with a one-line purpose, followed by a clean, structured Args block. Every sentence is informative and adds value without unnecessary verbosity. The format is standard and easy to parse.

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 3-parameter rename operation, the description covers purpose, parameters, and the overwrite condition. It does not explain return values, but an output schema exists, so that is not required. Missing edge-case behavior (e.g., what happens if new_name exists and overwrite is false) is a minor gap, but overall the tool is well specified.

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 0%, so the description must compensate. It does: each parameter (old_name, new_name, overwrite) receives a plain-language explanation that adds meaning beyond the schema's property titles. It could be more detailed (e.g., constraints), but it is fully adequate for an agent to understand all three parameters.

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 verb ('Rename (move)') and resource ('a project directory') with explicit context ('within the workspace'). This distinguishes it from sibling tools like rename_file and move_file, which apply to files. The parenthetical '(move)' also clarifies that rename implies relocation, leaving no ambiguity about the tool's function.

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 establishes a clear context: it is for renaming project directories, not files. This implicitly tells the agent when to use it versus rename_file/move_file. However, it does not explicitly state when not to use it or provide alternative tool names, so it falls short of the full 'when/when-not' guidance.

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