rename_preset

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that a backup copy is kept and that the tool refuses Bambu cloud presets with guidance in the answer, but it does not cover permissions, failure modes, or whether the rename is reversible beyond the backup note.

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 two sentences and front-loads the core action. The second sentence is longer but earns its place by explaining the important cloud-preset restriction and the response behavior.

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 mutation tool with no annotations, no output schema, and fully undocumented parameters, the description is incomplete. It explains the cloud edge case well but leaves the meaning of 'kind' and the expected response shape largely to inference.

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?

All three parameters have 0% schema description coverage, so the description must compensate. It only implies that 'name' and 'new_name' relate to renaming, and never explains what 'kind' means or what values it accepts, leaving a required parameter effectively undocumented.

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 states a specific verb and resource: 'Rename one of your user presets'. It also distinguishes the operation from cloud-preset handling by explaining that Bambu cloud presets cannot be renamed from here, which helps separate this tool from general preset editing.

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 implies when the tool applies by limiting it to user presets and explicitly excluding Bambu cloud presets. However, it does not name alternatives such as edit_preset or explain the relationship to delete_preset/search_presets, so the agent must infer the broader tool-selection context.

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