clickup_time_start

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

Discloses key behavior: if a timer is already running, it will be stopped first. Also notes return value. Lacks mention of permissions or rate limits, but with no annotations, the description adequately covers behavioral traits.

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 sentences, each adding unique value (purpose, auto-stop, pairing, return). Front-loaded with primary action. No 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?

Explains the action, side effect, companion tools, and return type. Sufficient for an agent to use correctly, though error handling is not addressed.

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 parameters are well-described in schema. Description adds no extra meaning beyond what schema provides, meeting baseline expectation.

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 the verb 'Start a live time-tracking timer for the authenticated user,' specifies the resource (timer), and distinguishes from siblings by naming clickup_time_stop and clickup_time_current.

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?

Provides explicit pairing with clickup_time_stop and clickup_time_current, giving clear usage context. Does not explicitly state when not to use, but the guidance is sufficient for correct selection.

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