delimit_data_backup

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

No annotations are provided, so the description must carry the full behavioral burden. It mentions backup with timestamp and destination, but lacks details on whether it overwrites existing backups, requires permissions, or if it creates the backup directory. Minimal disclosure.

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 concise sentence with no wasted words. It clearly communicates the action and destination.

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 simple one-parameter tool and the presence of an output schema (not described in the description), the description covers the basic operation. However, it lacks details on return values and behavioral traits, leaving some uncertainty for an agent. It is minimally complete.

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?

The input schema describes the parameter 'target' with 100% coverage (directory or file). The description adds that it backs up SQLite and JSON data files, providing extra context on acceptable file types, but the schema already covers the parameter meaning sufficiently. Baseline 3 is appropriate.

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 it backs up SQLite and JSON data files to a specific directory with a timestamp, which indicates the tool's purpose and resource. However, it does not explicitly differentiate from sibling tools like delimit_data_migrate, but the specific mention of backup and file types provides enough clarity for purpose.

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 guidance on when to use this tool versus alternatives like delimit_data_migrate or delimit_data_validate. The description only states what it does, not when it should be chosen.

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