clickup_start_time_tracking

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

No annotations exist, so the description carries the full burden. It usefully discloses the one-timer-at-a-time constraint, but leaves open what happens when a timer is already running (error, replacement, or silent no-op), whether the operation is idempotent, and what is returned.

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?

Four short sentences, front-loaded with the action and followed by capabilities, a constraint, and a caution. Nothing is padded, though the final advisory sentence is slightly redundant with the schema's own 'omit for best compatibility' note.

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 mutation tool with no annotations and no output schema, the description covers the core action and the key concurrency constraint. It still omits failure behavior, permission needs, and what the agent gets back, which matters for a tool that can conflict with a running timer.

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 each of the five parameters is already documented in the schema and the baseline is 3. The description adds only a light usage hint ('omit extra parameters unless specifically needed') that is not parameter-specific.

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?

States a specific verb and resource ('Start time tracking on a task') that an agent can distinguish from stop_time_tracking and add_time_entry without opening the schema. It doesn't explicitly name sibling tools, but the action is unambiguous.

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 implies when to use it (starting a timer on a task) and adds a constraint ('Only one timer can be running at a time'), but it never names alternatives like stop_time_tracking or add_time_entry, nor says when a logged time entry is preferable to a live timer.

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