Remove a template permanently to clean up unused designs. This action is irreversible and stops any batch jobs or experiments using that template.
Permanently delete a template. This action cannot be undone. WARNING: Any batch jobs, experiments, or bindings using this template will stop working.
| Name | Required | Description | Default |
|---|---|---|---|
| templateId | Yes | The template UID to delete |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It clearly discloses the destructive nature (permanent, cannot be undone) and cascading impact on dependent entities, which is essential for an agent deciding to invoke this 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?
Two concise sentences with critical information front-loaded: action, irreversibility, and warning. Every word earns its place.
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 single-parameter delete operation with no output schema, the description covers all necessary context: what it does, that it's irreversible, and what consequences occur. No gaps.
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 100% with a clear parameter description ('The template UID to delete'). The tool description adds no further detail about the parameter beyond confirming it identifies the template, resulting in a baseline score of 3.
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 clearly states the action ('Permanently delete a template') with a specific verb and resource. It distinguishes from sibling tools like pictify_create_template and pictify_update_template by emphasizing deletion.
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?
Explicitly warns about irreversibility and side effects ('Any batch jobs, experiments, or bindings using this template will stop working'), guiding the agent on when to use (only when permanent deletion is intended) and implications.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.