clone_feature_template

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

No annotations are provided, so the description carries the full behavioral burden. It says nothing about side effects, permissions, whether cloning is idempotent or fails on an existing name, or what artifact gets created and where. For a mutating scaffolding tool this is a notable gap.

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?

A single front-loaded sentence with no filler and the key resource named early. It is efficient, though too brief to count as fully optimized given the tool's complexity.

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 mutation tool with zero annotations and no output schema, the description supplies only the one-line purpose. Missing are prerequisites, resulting artifact, name collisions, and error behavior — all of which matter for correctly invoking a scaffolding operation.

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 100%, so all three parameters (featureName, description, templateName with its default) are already documented in the schema. The description adds no format, naming-convention, or default-override detail beyond that, which is the expected baseline.

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 description states a specific verb (clone) and resource (the Nstok-feature-template) plus the outcome (initialize a new feature repository). It is clear, but does not differentiate itself from siblings such as create_feature or clone_app_template, which perform adjacent scaffolding work.

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 instead of create_feature, create_feature_plan, or clone_app_template, nor any prerequisite or ordering information (e.g. whether an app must already exist). The agent must infer the workflow.

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