clickup_get_bulk_tasks_time_in_status

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

With no annotations, the description carries the burden and delivers two useful disclosures: the return shape (a map of task IDs to status history and current status time data) and a hard workspace prerequisite (the 'Total time in Status' ClickApp must be enabled). It does not cover rate limits or pagination, keeping it from a 5.

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?

Three tight sentences: purpose first, return format second, prerequisite last — appropriately front-loaded with no filler. Slightly cramped phrasing ('current status time data') but nothing wasted.

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 two-parameter read tool with no output schema, the description covers purpose, the return structure, and a critical enablement prerequisite. An agent could call it correctly; only pagination/rate-limit behavior is unaddressed, a minor gap.

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 task_ids (1-100) and workspace_id are already fully documented in the schema. The description's 'up to 100 tasks' merely restates maxItems and adds no syntax or format detail 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 (get) and resource (time multiple tasks spent in each status), scoped as a bulk operation up to 100 tasks. It implicitly distinguishes itself from the single-task sibling via 'bulk' and 'multiple tasks', but never names clickup_get_task_time_in_status explicitly.

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?

The 'bulk operation, up to 100 tasks' framing implies when to use this over the single-task variant, and the ClickApp prerequisite is a real gating condition. However, it never states when NOT to use it or points to the single-task alternative by name, so routing is inferred rather than stated.

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