backlog

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

No annotations provided, so description carries full disclosure burden. Explains critical behavioral traits: tasks are 'removed from the active database' (destructive side effect), 'can be loaded later with task_archive_load' (recovery mechanism), and 'keeping the active set small and fast' (performance rationale). Deducts 1 point for not explicitly stating if operation is atomic or reversible.

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 earning its place: 1) action + scope + performance benefit, 2) behavioral side effects + recovery path, 3) usage classification + alternatives. Well structured with front-loaded action.

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?

Given no annotations and no output schema, description adequately covers safety profile (removal from active DB), recovery mechanism (task_archive_load sibling), performance context, and sibling differentiation. No critical gaps for a maintenance operation tool.

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 detailed parameter description including default value (90) and examples. Description mentions 'older than N days' which aligns with schema but adds no additional semantic detail beyond what the schema already provides. Baseline 3 appropriate when schema does heavy lifting.

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?

Description uses specific verb 'Move' with clear resource scope 'completed and deleted tasks older than N days' and destination 'quarterly archive segment'. Explicitly distinguishes from sibling tools task_delete/task_purge by contrasting bulk vs individual operations.

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 states 'This is a bulk maintenance operation — for removing individual tasks, use task_delete or task_purge instead.' Provides clear when-to-use (bulk archival) and when-not-to-use (individual removal) with named alternatives.

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