edit_preset

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

With no annotations, the description carries the full burden and delivers: a backup copy is kept, null values revert to the parent preset, changes only appear in Bambu Studio after a restart, and the change is uploaded to Bambu cloud if the preset exists there. These are exactly the side-effect, reversibility, and propagation facts an agent needs before mutating shared state.

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?

Purpose and the backup guarantee are front-loaded in the first clause, with semantics following. The content is dense but nearly all of it earns its place; the extruder-variant detail is essential rather than filler, though the formatting is one unbroken block.

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 a free-form nested object parameter, the description covers reversibility, propagation delays, cloud sync, and the read-only system-preset constraint. Combined with the parameter detail, an agent has enough to call it correctly and anticipate consequences.

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 coverage is 0%, and the description compensates for two of three parameters in depth: it enumerates the 'kind' values (filament | process | printer) and fully specifies the 'values' object, including per-extruder list form, null-to-remove semantics, and concrete examples. The 'name' parameter's matching behavior (exact string, case sensitivity) is never addressed, which keeps it below a 5.

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 ('Change settings of one of your user presets') plus a scope qualifier ('directly, without a project'), which separates it from the save_*_preset and rename_preset siblings by implication. It does not explicitly name those siblings, so the distinction is clear but not spelled out.

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 gives a concrete precondition and exclusion: 'Bambu system presets are read-only: save a user preset from them first', which tells the agent when this tool will not work and what to do instead. It stops short of naming alternatives such as rename_preset, delete_preset, or list_user_presets for related operations, so guidance is clear but incomplete.

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