save_filament_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: the preset appears only after a Bambu Studio restart, new filaments get their own filament id so they can be assigned to an AMS slot, variants keep RFID matching, replace=True preserves the filament id so AMS slots stay valid and keeps a backup copy, and nothing is overwritten otherwise.

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?

Front-loaded with the core action and its effect, then mode distinctions and replace semantics. Dense but every sentence conveys distinct behavior; the parenthetical field list is the only mildly expendable element.

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 3-parameter mutation tool with no annotations and no output schema, the description covers the meaningful effects: id assignment, AMS implications, restart requirement, and overwrite protection. The remaining gap is what 'slot' identifies and what happens on invalid slot/name.

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%, so the description must compensate. The replace parameter is fully explained (updates an existing preset by name, keeps filament id, keeps a backup, never overwrites otherwise), and 'name' is implied to be the preset name, but 'slot' is never clarified—AMS slot index, printer scope, or something else—so a key parameter remains ambiguous.

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?

States a specific verb+resource: save the filament of a slot with the project's per-slot changes (temperatures, flow ratio, pressure advance, plate temperatures) as a Bambu Studio user preset. It is clearly distinct from save_process_preset, save_printer_preset, and edit_preset/rename_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?

Explains the two modes explicitly: a new filament (from a Generic preset or another vendor) is saved like Bambu Studio's Create Filament, while changes to a Bambu filament become a variant. It also directs the agent to replace=True when updating an existing preset after a calibration instead of creating a duplicate.

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