save_user_preset

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

With no annotations, the description carries the full burden and does disclose valuable traits: overwrite semantics, GUI visibility requiring a slicer restart, and inheritance with a diff-only settings payload. It omits what happens on name collisions, validation failures, or what the call returns.

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 short sentences with zero filler, and the primary action is front-loaded before the parameter notes. The telegraphic 'inherits: ...; settings: ...' phrasing is compact but slightly clipped.

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 4-required-param mutation tool with nested objects, no annotations and no output schema, the description covers the tricky semantics (overwrite, inheritance, diffs) but leaves the meaning and valid values of 'kind' entirely to the agent's guesswork.

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; it does define 'inherits' (parent preset name) and 'settings' (only keys differing from the parent), which are the two non-obvious parameters. 'kind' and 'name' — 'kind' especially, a free-form string with no enum — are left unexplained.

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?

A specific verb ('Create/overwrite') plus resource ('a user preset') and an effect ('shows up in the GUI'). It does not distinguish itself from siblings like list_presets or get_preset, but the action itself is unambiguous.

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 conveys the post-condition (restart the slicer to see it) but gives no guidance on when to use this versus get_preset, list_presets, or open_in_slicer, and no prerequisites (e.g. whether the parent must already exist).

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