stop_task

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

No annotations provided, but description fully explains effects: clears start field, stops time tracking if Timewarrior installed, supports dry_run for preview. States it does not complete or delete the task.

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?

Six sentences, no wasted words. Front-loaded with main action, then subsidiary details. Each sentence adds 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?

Given no annotations and 2 parameters, description covers action, behavior, dependencies, and role. Doesn't describe output schema but one exists, so not required. Missing a bit on parameter details.

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 0%, so description should compensate. It explains dry_run parameter but not uuid. While uuid is standard, the description could briefly note it uniquely identifies the task.

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?

Clearly states it deactivates a task by clearing its start timestamp. Distinguishes from siblings like start_task and complete_task by explaining what it does and does not do.

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 says when to use (stop tracking work sessions), pairs with start_task, and alternative complete_task for marking done. Mentions required CONTRIBUTOR role.

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