create_full_backup

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'create a full account backup' without mentioning potential side effects, required permissions, notification behavior, or whether it overwrites existing backups. The schema hints at email notification and FTP/SCP destination, but the description adds no such context.

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 short sentence, which is front-loaded and easy to parse. However, it is under-specified—it lacks necessary detail about scope, destination, and notification, so the brevity comes at the expense of completeness.

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?

Given the tool's complexity (7 params, no annotations, no output schema, and many sibling backup tools), the description is severely incomplete. It does not explain what a 'full account backup' includes, where it is stored, how to retrieve it, or what happens with the provided email/FTP/SCP parameters. The sibling 'list_backups' tool suggests a way to verify, but this is not mentioned.

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% (all 7 parameters have descriptions in the schema), so the baseline is 3. The description itself adds no parameter details, but the schema already documents each field. It does not explain how parameters relate to each other (e.g., which are required for FTP/SCP).

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 action ('Create') and a specific resource ('a full account backup'), which clearly differentiates it from sibling tools like create_database_backup, create_homedir_backup, and create_email_backup. However, it does not elaborate on what 'full' includes, so it is not as detailed as the high-calibration example.

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 gives no guidance on when to use this tool versus the many other backup-related tools in the sibling list. There is no mention of alternatives, exclusions, or prerequisites (e.g., FTP/SCP credentials needed if destination is ftp/scp).

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