backup_report

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

Discloses key non-destructive behavior: original untouched, returns backup path, and automatic backup opt-in. Could mention error handling or failure scenarios, but adequate given no annotations.

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?

Three concise sentences, front-loaded with the core action. Every sentence adds value without 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?

Complete for a simple backup tool: explains action, usage context, return value, and configuration. No gaps given the simplicity and lacking output schema.

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?

Adds meaning beyond the input schema: the path parameter is the source for the backup, and the description specifies the backup filename pattern. Schema coverage is 100%, and the description enriches the context.

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 action: copying a report to a timestamped .bak file, preserving the original. It distinguishes itself from siblings as a checkpoint before destructive operations like remove_* and rename_parameter.

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?

Explicitly recommends using this tool before a destructive batch, naming specific sibling patterns. Also mentions the optional automatic backup via environment variable, providing clear usage context.

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