Create a backup

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

The description adds real value beyond annotations by disclosing the side effect's location: files are written to the router's own file system (not downloaded to the caller). However, with idempotentHint=false it never warns that an existing file of the same name may be overwritten, nor does it mention possible size/time cost of a full config backup, which are the traits an agent most 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?

A single front-loaded sentence with no filler; the action, both artifact types, and the destination are all in the first clause.

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?

With no output schema, the description should say what the agent gets back (created file names/paths, or confirmation) and whether a backup can overwrite an existing file; neither is covered. For a write tool that creates persistent files, this leaves a meaningful gap, though the schema carries the parameter detail well.

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%, so all four parameters (name, device, password, exportScript) are already documented in the schema, making 3 the baseline. The description's only added meaning is the pairing of 'binary backup' with password encryption and 'text export' with exportScript, which is useful but already inferable from the schema.

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?

States a specific verb (Save) and resource (binary .backup and/or text .rsc configuration export) plus the destination (the router's file system). No sibling tool does backups, so no differentiation is needed, but the description never says how this relates to the read-oriented siblings (e.g., that it writes rather than reads config).

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?

Usage is only implied: the 'and/or' phrasing hints that either artifact can be produced, and the schema's exportScript default covers the choice, but there is no explicit when-to-use context (e.g., before upgrades), no prerequisite that a device must be configured, and no guidance on when a password-protected binary backup is preferable.

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