merge_decoration_preset_branches

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

With no annotations, the description carries the full behavioral burden, and it does add genuinely relevant context: on success it opens an interactive 3D stage, oversized meshes are auto-decimated, and hosts without panel support get a browser link. However, it never discloses the destructive/irreversible nature of a branch merge, conflict handling, or permission requirements, which are the traits an agent most needs for a mutation tool.

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 purpose is front-loaded, but two large blocks are promotional ('Everything in Free... Requires Kiln Pro. Upgrade: <url>') and the inline 3D stage behavior is stated twice with overlapping wording. Much of the text does not help an agent invoke the tool.

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 5-parameter mutation tool with no annotations, no output schema, a nested object parameter, and 0% schema description coverage, the description should explain conflict resolution, ancestry, and return behavior. Instead it covers only the 3D stage, leaving the core merge semantics and most parameters unexplained.

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% across 5 parameters, including a nested 'resolutions' object, so the description must compensate. It only gestures at source and target branches (mapping to source_branch_id/target_branch_id) and says nothing about ancestor_preset_version_id, merged_by, or the structure of resolutions, leaving most parameter meaning undocumented.

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 opening sentence gives a clear verb+resource: merge source_branch into target_branch. It is distinguishable from sibling merge tools only through the tool name ('decoration_preset'), not the description text, which speaks generically of 'source_branch' and 'target_branch'. The qualifier 'semantically' is left unexplained.

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?

There is no guidance on when to use this versus merge_design_branches, merge_feature_branches, or cherry_pick_decoration_modification, and no mention of the related detect_decoration_preset_merge_conflicts tool. The 'Requires Kiln Pro' line reads as an upsell hook rather than a clear prerequisite statement, so the agent still cannot tell when this tool is the right choice.

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