create_backup

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

With no annotations provided, the description carries the full burden and does so thoroughly: it discloses that this is a guarded WRITE operation blocked unless `MIKROTIK_ALLOW_WRITE=true`, that `confirm` controls preview vs execution, that existing files cause an error instead of being overwritten, and that `password` is a file-encryption option never returned or journaled. These are exactly the behavioral traits an agent needs.

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 front-loaded with the purpose and command, then walks through follow-up, parameter caveats, and write-guard behavior. It is appropriately sized for a guarded write tool with no annotations, though the reference to `guard.create_backup`'s docstring is a slight indirection that could be trimmed.

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 that an output schema exists, the description need not explain return values, and it focuses on behavior: guard requirements, confirmation workflow, no-overwrite policy, and password redaction. The only missing piece is any guidance on `device_name`, but otherwise it is complete for a write tool of this complexity.

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 0%, so the description must compensate. It explains `password` (RouterOS file encryption, never exposed) and `confirm` (preview versus actual creation) in detail, and implies `name` as the file identifier, but `device_name` is not described at all. Two and a half of four parameters are given meaning, leaving a notable gap.

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 a RouterOS system backup) and the exact resource (binary `.backup` file on device storage), even including the underlying command. It also distinguishes itself from `list_backups`, which is the follow-up verification tool, so an agent can tell the two apart without opening either schema.

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?

It gives clear invocation guidance: use `confirm=False` for a preview, then `confirm=True` to execute, and check results with `list_backups`. There is no explicit 'when not to use' alternative for creation, but the write guard and the no-overwrite behavior implicitly set the context.

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