create_decoration_preset_branch

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

No annotations exist, so the description carries the full behavioral burden. It does disclose one meaningful trait — the paid-tier gate — which an agent needs before invoking. It says nothing about what the fork copies, whether it consumes decoration quota, or what happens on a nonexistent preset_version_id.

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?

Only the first sentence describes the tool; the remaining three lines are marketing copy ('Everything in Free, plus calibration that learns your printer...') and a tracking-tagged upsell URL. The Pro requirement is worth one clause, not a third of the definition.

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?

A 6-parameter mutation tool with no annotations and no output schema needs substantially more: which fields are required, what the base version defaults to, and what a successful fork returns. The description covers only the tier gate.

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 17% across 6 parameters, so the description must compensate and does not. 'From a specific preset version' loosely hints at base_preset_version_id, but parent_branch_id, created_by, and annotation are neither documented in the schema nor clarified here.

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 first sentence gives a clear verb and resource — forking a new branch from a specific preset version — which is enough for an agent to distinguish it from sibling creation tools like create_decoration_preset. It stops short of naming related siblings (list_decoration_preset_branches, rebase_preset_branch), so differentiation is only partial.

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?

The description implies usage through the fork concept and adds a real prerequisite ('Requires Kiln Pro'), but never says when to fork versus create a fresh preset, nor which sibling to use for listing or merging branches. The upgrade URL is an upsell, not usage guidance.

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