archive-completed-tasks

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

The description discloses the core behavior (moving completed tasks) and the 'preserving historical tasks' trait, but with no annotations, it does not cover side effects like whether the move is reversible, permissions required, or failure behavior. The description carries the full burden and only partially satisfies it.

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 concise sentences front-load the action and purpose with no unnecessary detail. Every word earns its place, and the structure efficiently communicates the tool's function.

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?

The description covers the main action and use case, but the absence of an output schema and annotations means it does not explain return behavior or edge cases, leaving some context gaps. For a mutation tool with no output schema, a bit more detail on expected results would improve completeness.

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 descriptions cover all four parameters with clear definitions (e.g., olderThanDays default 90), so the description's mention of 'specified number of days' adds little beyond the schema. The schema already provides parameter-level semantics effectively.

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 moves completed tasks older than a specified number of days from a source list to a target archive list, distinguishing it from siblings like delete-task (which removes tasks) or update-task (which changes task fields). The verb 'Move' and resource 'completed tasks' are specific and unambiguous.

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?

The phrase 'Useful for cleaning up active lists while preserving historical tasks' provides clear context for when to use this tool, implying a maintenance/cleanup scenario. It does not explicitly describe when not to use it or name alternatives, but the context is clear enough for typical use.

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