archive_task

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

With no annotations, the description carries full burden. It discloses that the operation is a soft delete, what it affects (listings and board), and that it returns the archived task. However, it does not mention reversibility (whether unarchive is possible) or permission requirements, which would enhance transparency.

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 extremely concise with three sentences, no unnecessary words, and front-loads the key action. Every sentence adds value: defines the operation, clarifies it is soft delete, and states the return value.

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 tool is simple (one parameter), has an output schema, and the description covers the core effect and return. However, it lacks information about whether the operation is reversible or if there are side effects (e.g., on dependent tasks). Given the low complexity, it is mostly complete.

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 0% for the single parameter task_id. The description does not explain the parameter's meaning, type, or role beyond what the schema provides. Since coverage is low (<50%), the description should compensate, but it fails to add any parameter-specific information.

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 verb 'archive' and resource 'task', and explicitly defines it as a soft delete. It distinguishes from siblings by specifying that the task disappears from listings but remains in the database, whereas sibling tools like edit_task, move_task, or delete (not present) have different effects.

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?

No explicit guidance on when to use this tool over alternatives. The description implies usage for hiding tasks without permanent deletion, but does not provide explicit when-to-use or when-not-to-use context relative to siblings like edit_task or move_task.

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