cfg_backup

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

Discloses backup location (next to original or backup_dir), allowlisted directories for config_path, and naming format. No annotations provided, so description carries full burden; it covers key behaviors without contradictions.

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?

Concise with a clear summary and bulleted parameter list. Every sentence adds value, no redundancy.

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?

Explains return value (backup path for rollback), covers parameters and constraints. Could mention writability of backup_dir, but sufficient for a simple backup tool.

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 has 0% description coverage; description compensates by explaining config_path must be absolute and in allowlisted directories, and backup_dir is optional. Adds meaningful context beyond schema types.

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?

Clearly states it copies a config file to a timestamped backup, with explicit naming convention and return value. Distinguishes from sibling cfg_rollback by mentioning its output can be used for rollback.

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?

Provides context that the backup path is intended for cfg_rollback, implying usage. Does not explicitly state when not to use or list alternatives, but the purpose is clear.

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