archive_checklist

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

Describes that checklist is moved to archive directory and marked Archived. No annotations, but description covers main behavioral effect without contradictions.

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 sentences: first specifies action and identifier types, second explains consequence. No extraneous text, highly 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?

Adequately covers purpose and effect for a simple tool with one parameter and no output schema. Missing error handling details, but not essential for basic use.

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?

Single parameter documented in schema (100% coverage). Description repeats schema content without adding further nuance, meeting baseline.

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 archives a checklist using goal name, substring, or numeric ID, and explains the outcome. Distinguishes from siblings like activate_checklist and init_checklist.

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?

Implicitly guides when to use (to archive a checklist), but no explicit when-not-to-use or alternatives mentioned. Context suggests distinct purpose among siblings.

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