create_decoration_preset

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

With no annotations, the description carries the full burden, but it does contribute two real behavioral facts: the operation is branch-scoped and it requires Kiln Pro (a plan/precondition gate). It still omits mutation semantics, what versioning does to prior versions, idempotency, and failure behavior, leaving meaningful gaps.

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 first sentence is well front-loaded and does the essential work. The second paragraph is marketing framing ("Kiln Pro would save this as...") that restates the purpose rather than adding operational information, and the upgrade URL, while short, is promotional.

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 15-parameter mutation tool with no annotations and no output schema, the definition is thin: no parameter guidance, no statement of what is created/returned, and no branching/versioning semantics. The plan precondition is the only material addition, leaving the agent under-informed for correct invocation.

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 description coverage is only 27% across 15 parameters, so the description needed to compensate and does not mention a single parameter (name, pattern_family, pattern_id, or the versioning-related preset_id/parent_preset_version_id). An agent gets no extra meaning beyond the schema's terse titles.

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 and resource with scope: "Create or version a decoration preset on a branch." An agent immediately knows this produces a persisted, versioned preset. It does not, however, name or contrast itself against close siblings like save_decoration, create_decoration_preset_branch, or apply_decoration_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?

"Create or version" implies the two conditions under which this is used, and "ready to apply to any future design" hints at reusability, so usage is implied. But there is no explicit when-to-use-vs-alternative guidance and no exclusions relative to the many sibling preset tools.

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