rename_entity

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

The annotation only provides destructiveHint: true. The description adds a valuable behavioral detail by stating that existing targets are refused, meaning the tool will not overwrite an existing file or folder. It does not cover broader effects like broken references, but that is reasonable for a simple rename operation.

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, well-structured sentence that leads with the action and then includes two high-value constraints. Every word contributes meaning, with no redundant or vague filler.

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 two-parameter tool with no nested objects and no output schema, the description covers the core operation and the most important edge case (refusing existing targets). It could mention success/error behavior or permissions, but the operation is simple enough that the current description is nearly complete.

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 for parameter meaning. It clarifies that `path` refers to an existing entity and that `new_name` is a new name within the same parent, but it does not specify exact formats, constraints, or whether extensions or path separators are allowed.

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 identifies the operation (rename), the resources (file or folder), and the constraint (within its current parent). It also adds a distinguishing behavior (refuses existing targets), which helps separate it from sibling tools like create_file, delete_entity, or edit_file.

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 intended use case is implied: renaming an existing file or folder without moving it. However, it does not explicitly state when to prefer this tool over siblings, nor does it mention alternatives such as using create_file for new files or delete_entity for removals.

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