Delimit Data Backup

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

Discloses side effects beyond the annotations: writes timestamped copies to a specific location, captures a restore point, and does not claim to modify original files. The annotations destructiveHint=false and readOnlyHint=false are consistent with this behavior; no contradiction.

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 well-structured and front-loaded: purpose, when to use, when not to use, sibling contrast, and side effects are each given their own concise labeled section. Every sentence carries useful routing or safety information with no filler.

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?

For a simple one-parameter tool with an output schema and safety annotations, the description covers purpose, trigger conditions, exclusions, alternatives, side effects, and destination. Nothing an agent needs to decide whether to call it or to call it safely is missing.

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 100% and the schema already documents target as the directory or file to back up and the default '.'. The description adds domain context about backing up SQLite and JSON data, but it does not materially expand parameter-level semantics beyond 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?

Opens with a specific verb and resource: 'Back up SQLite and JSON data files to ~/.delimit/backups/.' It also explicitly contrasts itself with delimit_data_validate and delimit_data_migrate, so an agent can distinguish it from the most similar siblings.

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 explicit when-to-use guidance ('before a risky migration or refactor'), when-not-to-use guidance ('to validate data integrity... apply migrations'), and names the exact alternatives. This leaves no ambiguity about tool selection.

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