clickup_create_time_entry

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

Goes beyond annotations by specifying the HTTP method (POST), endpoint, return value (confirmation string with key fields), and detailed error handling (400/404, specific error code TIMEENTRY_072 and workaround). Annotations already indicate non-readonly and open-world, but description adds rich behavioral context.

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-organized with sections (when to use, examples, error handling). Front-loaded with purpose. Slightly long but each sentence adds value; no fluff.

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?

Given the complexity (multiple params, mutual exclusivity, default values, error codes) and the presence of an output schema, the description covers the key behavioral aspects, return format, and error scenarios comprehensively.

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 0% per context, but the description provides examples showing duration/stop mutual exclusivity and notes default team_id. However, many parameters (tags, assignee, custom_task_ids) are not individually described; the schema itself provides descriptions, so the description adds limited additional semantics.

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 starts with 'Log a completed (already-finished) time entry.' which is a specific verb and resource. It clearly distinguishes from sibling tool clickup_start_time_entry by stating when not to use (for running timers).

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?

Explicitly states when to use (backfilling time, logging completed blocks) and when NOT to use (starting a running timer, directing to alternative clickup_start_time_entry). Examples further clarify usage.

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