ck_memory_archive

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

The description adds that the operation is a write that marks as archived (not deleted) and excludes from future searches. Annotations confirm non-destructive nature. Lacks details on reversibility or return value, but output schema exists.

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 sentences, each essential: action definition, operational detail, usage guidance. No redundancy or 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?

Covers key behavioral aspects and usage context. References sibling tools for alternatives. With output schema present, return value is handled. Minor omission: no mention of error conditions or permissions, but adequate for the tool's simplicity.

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 coverage is 67% with descriptions for project_root and session_id. The description adds value for memory_id by specifying it comes from ck_memory_record or ck_memory_search, improving meaning beyond the schema's type-only declaration.

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 memory record, excluding it from search results. It also distinguishes from the update operation by directing users to ck_memory_record for updates.

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 specifies when to use: for stale, superseded, or no-longer-relevant records. Provides clear alternative: use ck_memory_record for updating content instead of archiving.

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