Creates a backup of all files in the cPanel home directory to preserve account data before changes, migrations, or recovery.
Create a backup of the home directory files
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v2.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It states only that a backup is created, but does not disclose whether it overwrites existing backups, whether it is synchronous, where the backup is stored, naming conventions, or any other side effects. For a mutation operation with zero annotation coverage, this is a significant 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?
The description is a single sentence with no filler words: 'Create a backup of the home directory files'. It is concise and immediately conveys the purpose with no waste.
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?
Despite the low complexity (0 parameters), the description is very sparse. There is no output schema and no annotations, so the description should provide some context about what happens after the backup is created, such as whether a backup ID is returned, where the backup is stored, or how to verify success. The description is only minimally complete for a simple action.
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 tool has zero parameters, so the schema is fully covered (100%). The baseline for zero parameters is 4, and there is nothing for the description to add about parameter semantics. The description does not need to compensate for any undocumented inputs.
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 verb 'Create' and the resource 'backup of the home directory files', which distinguishes it from database, email, and full backups. However, it does not explicitly distinguish from 'create_full_backup', which may include home directory files, so it is clear but not fully differentiated.
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 implies usage when the user wants to back up home directory files, but it provides no explicit when-to-use guidance or references to sibling tools like 'create_full_backup' or 'create_database_backup'. There is no exclusion or alternative mentioned, so only the implied context from the resource name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.