ssh_backup_schedule

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

Discloses mutation of remote filesystem and crontab, and the need for root. Mentions retention deletion. However, it does not specify idempotency (e.g., overwriting an existing schedule) or error behavior.

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?

Two concise, front-loaded sentences. Every word adds value, with 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?

Covers core mechanism, requirements, types, and retention. Missing details on idempotency and output, but adequate given no output schema and no annotations.

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 baseline is 3. The description adds context about the retention default (7 days) and the behavior of the generated script, slightly exceeding 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?

The description clearly states the tool schedules recurring backups by writing a bash script and installing a crontab entry. It distinguishes from sibling tools like ssh_backup_create (one-time) and ssh_backup_list/restore.

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?

No explicit guidance on when to use this tool versus alternatives. It implies usage by describing the function, but does not mention when not to use it or point to siblings for one-time backups.

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