delete_template
Delete a page template from a Collective in Nextcloud.
Instructions
Delete a page template.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| templateId | Yes | ||
| collectiveId | Yes |
Delete a page template from a Collective in Nextcloud.
Delete a page template.
| Name | Required | Description | Default |
|---|---|---|---|
| templateId | Yes | ||
| collectiveId | Yes |
Changes observed during successful MCP inspections.
v0.2.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description does not disclose whether deletion is permanent, whether it affects pages using the template, or any other side effects, despite the destructiveHint annotation.
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 description is a single, concise, and clear sentence with no unnecessary words.
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?
The description is minimal and lacks important context such as permanence, impact on associated data, or prerequisites, making it incomplete for a destructive 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?
The parameter names (templateId, collectiveId) are self-explanatory and the schema fully covers them, but the description adds no additional context about their relationship or usage.
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 (delete) and the resource (a page template), making its purpose immediately obvious.
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 provides no guidance on when to use this tool over other delete operations (e.g., delete_page, delete_collective) or any prerequisites or side effects.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.