Rename preset

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

The description explicitly states 'delete the old', which is a destructive operation, while annotations set destructiveHint=false. This is a direct contradiction and dominates the otherwise useful disclosure of the multi-step copy/select/delete behavior.

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 front-loads the purpose and then lists the exact behavioral steps. Every word contributes, 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 simple rename tool, the description covers the main operation and its side effects, including the deletion of the old preset. However, it does not explain the exact value or format for the `type` parameter, nor any return value or error conditions, leaving some ambiguity for an agent.

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 schema has 0% parameter descriptions, but the description compensates by mapping old_name/new_name to the old and new preset names and implying the type is 'USER' preset. It does not explicitly define allowed values for `type`, but enough meaning is provided for most use.

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 'Rename a USER preset' with a specific verb and resource, and then details the exact composite steps (save copy, select, delete old). This distinguishes it from siblings like edit_preset, save_preset, and delete_preset.

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?

It clearly indicates this applies to USER presets and explains the rename workflow as a copy-select-delete operation. It does not explicitly name exclusions or alternatives, but the context is sufficient for selecting this tool over related preset tools.

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