Save preset (overwrites stored settings)

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

Annotations already indicate destructiveHint=true, but the description adds crucial context: it overwrites stored settings, is visible in the GUI immediately, and the detach parameter changes inheritance behavior. It also discloses the permission requirement and physics-check prerequisite, going well beyond annotation hints.

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?

Two sentences effectively cover purpose, parameters, prerequisites, and permission. The main action is front-loaded, and no words are wasted. The structure is logical: action first, then constraints and safety checks.

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 save operation with no output schema, the description sufficiently covers the action, parameter semantics, necessary preconditions (check_profile_physics), and permission requirements. It is complete enough for an agent to decide when and how to use the tool correctly.

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 carries full responsibility. It explains the 'type' parameter values (print, filament, printer) and the 'detach' parameter's meaning (standalone vs inheriting base preset). The 'name' parameter is self-explanatory but the others are well clarified.

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 the tool saves currently edited settings as a named user preset, with create or update behavior and immediate GUI visibility. It distinguishes itself from sibling tools like edit_preset, rename_preset, delete_preset, and select_preset by specifying this is for saving the current editing session.

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?

Explicitly instructs to run check_profile_physics first and not to save when verdict=blocked, providing a clear precondition and exclusion. It also mentions the required permission 'preset/save'. It doesn't explicitly name alternative tools for when not to use it, but the context is clear.

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