start_task

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

No annotations provided, so description carries full burden. It discloses behavioral traits: sets start field, affects reports, triggers Timewarrior time tracking with task tags, supports dry_run for preview, and specifies it does not complete or delete.

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?

Description is concise, front-loaded with primary purpose, and structured in clear bulleted points. Every sentence adds value without redundancy.

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 but presence of output schema, description covers behavior, prerequisites, mutation behavior, dry run support, and relationships to sibling tools. Complete for effective use.

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%, but description adds context for dry_run parameter (preview without mutation). uuid is not described but is self-explanatory given the tool purpose. Missing details like uuid format or constraints, but overall adequate.

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 clearly states the verb (mark as active) and resource (task), and distinguishes from siblings like stop_task and complete_task by specifying that it does not complete or delete.

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 (to activate and start time tracking), and when not (does not complete/delete). Names alternatives (stop_task, complete_task) and mentions role requirement (CONTRIBUTOR).

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