Archive Completed Nodes

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

Annotations already indicate a mutation (readOnly=false) and non-destructive (destructive=false) operation. The description adds the 'updated before cutoff' condition but does not disclose reversibility, side effects, or what 'archived' means. No contradiction with annotations.

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?

The description is a single 11-word sentence, front-loaded with the action and resource. Every word earns its place without 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?

For a simple tool with 2 optional params and no output schema, the description covers the essential action and condition. Annotations and schema fill gaps. However, it could benefit from mentioning the effect of 'archived' or its relationship to cleanup tools.

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 100% with descriptive parameter entries. The description mentions 'cutoff threshold' but does not add meaningful detail beyond the schema for the two optional 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 uses a specific verb ('Flag') with a clear resource ('completed tasks') and condition ('updated before a specified cutoff threshold'), making it distinct from sibling tools like auto_prune_stale_tasks (which implies pruning) and complete_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?

The description implies usage for archiving old completed tasks but provides no explicit guidance on when to use this tool versus alternatives such as auto_prune_stale_tasks or get_stale_nodes, nor any exclusions or prerequisites.

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