Archive Plans

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

Discloses the destructive actions (moving files, removing index entries) and the dry run feature. Without annotations, the description carries the full burden and does so adequately, though more detail on reversibility could help.

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, no fluff, all essential information front-loaded.

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?

No output schema and no annotations, so description must cover more. It explains behavior and dry run but omits return value format and any prerequisites or side effects beyond those mentioned.

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%, so baseline is 3. The description adds context for dryRun but little beyond what the schema provides for other parameters.

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 (archive), the resource (old planning sessions), and the effect (moving files to archive/YYYY/ subdirectory and removing from Yggdrasil index). It distinguishes well from sibling tools like list_plans and promote_plan.

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 guidance on dry run vs execution mode, implicitly telling when to use (archive old sessions). However, it lacks explicit contraindications or alternative tool mentions.

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