cloud_clone_preset

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

With no annotations, the description carries the full burden, and it does add one real behavioral fact: the tool requires a Kiln Pro entitlement. Beyond that it says nothing about whether the clone overwrites existing local state, where the preset lands, or whether the operation is repeatable or reversible — instead the remaining sentences are product marketing.

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 earns its place. The two following sentences are tier/marketing copy and an upgrade URL that do not help an agent select or invoke the tool, and they dilute the front-loaded purpose statement.

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?

No annotations, no output schema, and an undocumented required parameter — the definition should be doing much more work. An agent cannot tell what the call produces locally or how it differs from the adjacent cloud_* clone and pull tools.

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 only 50% and preset_id has no schema description at all, so the description is the place to compensate — but it never mentions either parameter. It gives no hint of what preset_id refers to or what the 'remote' default of "default" means.

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 states a verb and resource ("Bootstrap local storage for a remote-only decoration preset"), which is more than a restatement of the name. However "bootstrap local storage" is vague about what is actually created locally (a preset copy? a branch?), and there is no differentiation from the many sibling clone/pull tools such as cloud_clone_design, cloud_clone_feature, or cloud_pull_preset_branch.

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 statement of when to use this tool versus cloud_pull_preset_branch, cloud_clone_design, or the other clone/pull siblings. The only contextual sentence is a paywall note ("Requires Kiln Pro"), which does not help an agent choose the tool.

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