clickup_add_time_entry

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the derived-value behavior ('tool will calculate missing values') and the required inputs, but says nothing about permissions, error cases, or what the call returns/converts side effects beyond creation.

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?

Front-loads the core action in the first sentence, then adds the parameter-combination rule and optional fields. Four short sentences with little waste, though the third sentence partly repeats the second's constraint.

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 an unannotated mutation tool with no output schema, the description covers the essential calling contract (required inputs, value-derivation) but omits return values or confirmation of what gets created, leaving a gap an agent might need when chaining calls.

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 the schema already documents all eight parameters including formats and the duration/end_time alternative. The description's restatement of the (start+duration) OR (start+end) rule adds convenience but no meaning beyond the schema, so baseline 3 applies.

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 ('Add a manual time entry to a task'), and the word 'manual' implicitly separates it from the timer-based clickup_start_time_tracking and the read-only clickup_get_time_entries. It does not explicitly name those siblings, 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?

Gives clear conditional usage: provide either (start + duration) OR (start + end), with the tool filling in missing values. It lacks an explicit 'use X instead when...' pointer to the timer tools, but the input-combination guidance is concrete and actionable.

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