archive_to_history

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

Discloses that both task and reports are moved, creates immutable date-sharded record, and documents date default behavior with override option. No annotations provided, so description carries full burden; it does well.

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?

Well-structured into two paragraphs: action overview then prerequisite/details. Every sentence is informative. Could be slightly more concise but overall efficient.

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 purpose, parameters, prerequisite, and output format hints (date-sharded path). Has output schema so return values not needed. Adequate for an agent to use correctly.

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 already describes both parameters (100% coverage). Description adds format examples for task_id and explains default behavior for done_date. Adds value beyond 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?

Clearly states the action: move a closed task from `_lifecycle/archive/` to deep history archive. Specifies source and destination directories and that all associated reports are moved together, distinguishing it from siblings like archive_task.

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 states prerequisite to call archive_task first. Implicitly differentiates from bulk_archive_to_history (single task vs bulk). Does not explicitly list when not to use, but context is clear.

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