time_tracking_start

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

No annotations are provided, so the description carries the behavioral disclosure burden. It discloses the one-timer constraint, which is a key behavior, but does not explain what happens when a timer is already running (e.g., error vs. auto-replace). It also does not mention return values or permissions.

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 three concise sentences with no fluff. The main action is front-loaded, and every sentence adds relevant information: purpose, constraint, and supported options.

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?

For a 5-parameter tool with no annotations and no output schema, the description is adequate but incomplete. It covers the core purpose and a key constraint, but fails to explain the behavior when a timer is already running or what the response contains. This leaves important gaps for an agent deciding to invoke it.

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%, so the baseline is 3. The description mentions 'description and billable status' as optional and refers to 'task' for task_id, but adds no additional syntax, format, or usage details beyond what the schema already provides.

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 'Start the timer on a ClickUp task,' which is a specific verb and resource. It distinguishes from sibling tools like time_tracking_stop and time_tracking_current, and mentions key attributes (one timer at a time, optional fields).

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 provides clear context by stating 'Only one timer can run at a time,' implying the need to check for an existing timer (time_tracking_current) and stop it (time_tracking_stop), but it does not explicitly name alternatives. No exclusions are given.

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