remove_task

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

With no annotations, the description must disclose behavioral traits. It mentions cleanup and warnings, which is helpful, but does not specify whether removal is permanent, if permission is required, or what the output contains (output schema exists but is not referenced).

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 short sentences, no fluff. The first sentence provides the core action, and the second adds key behavioral details (cleanup, warnings). Every word earns its place.

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 an output schema exists, the description need not detail return values. It covers the main action, cleanup, and dependency warnings. However, it could mention that it operates on the mise configuration early in the first sentence for immediate clarity.

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 the description adds no new meaning beyond the schema. Both 'task_name' and 'project_path' are self-explanatory. The description's mention of 'named task' slightly reinforces the parameter but does not add depth.

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 removes a specific task from a project, specifically from the mise configuration. This is a unique purpose among siblings like 'create_task' and 'prune_tasks', which handle creation or bulk removal respectively.

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 mentions cleanup and dependency warnings but does not provide explicit guidance on when to use this tool versus alternatives like 'prune_tasks' or 'validate_task_architecture'. The context of sibling tools implies it's for removing a single named task, but this is not stated.

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