clickup_start_time_entry

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

Goes beyond annotations by disclosing that duration in response is negative while running, that ClickUp allows only one active timer per user, and the 400 error scenario. Annotations (readOnlyHint=false, destructiveHint=false) are consistent.

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?

Well-structured with sections: summary, endpoint, when to use, when not to use, returns, example, error handling. Front-loaded and no unnecessary words.

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 tool with complex input (nested object), output schema, and annotations, the description covers purpose, usage, behavior, returns, and error handling. It is fully adequate for an agent to use correctly.

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?

Input schema has descriptions for each property, but the description adds a concrete example (params = {team_id: '123', tid: 'abc123', description: 'pairing session'}) which helps understanding. Schema coverage is 0% but schema itself has descriptions, so baseline is 3, and the example adds value.

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 starts an open-ended running timer for the authenticated user. Differentiates from sibling clickup_create_time_entry by specifying the open-ended nature versus timers with known duration. Also mentions the API endpoint.

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 'When to Use' (beginning live tracking with no known end) and 'When NOT to Use' (log known duration, check for active timer first with clickup_get_running_time_entry). Also covers error handling (400 indicates timer already running, use clickup_stop_time_entry).

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