clickup_get_running_time_entry

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

Annotations already indicate readOnly, idempotent, non-destructive. Description adds key behavioral details: negative duration for running timers, 'No timer' message, and output format options, enhancing transparency beyond annotations.

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?

Description is well-structured with clear sections and front-loaded purpose. Each sentence adds value, though slightly longer than minimal. No wasted 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?

Covers usage, behavior, return details, and error scenarios. With good annotations and sufficient parameter documentation, it provides a complete understanding for the agent. Output schema existence is noted but not needed given description.

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 already provides descriptions for all parameters (team_id, assignee, response_format). Description adds examples and error handling but does not significantly extend parameter meaning. Schema coverage is effectively high, so baseline 3.

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 clearly states the tool retrieves the currently running time entry for a user. It uses a specific verb and resource, and distinguishes from siblings like clickup_get_time_entries and clickup_start/stop_time_entry.

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 (before starting or stopping a timer) and when not to use (for historical entries, use clickup_get_time_entries). Also covers error handling for 403 permission issues.

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