clickup_get_task

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing. It does not state that this is a read-only operation, whether it requires auth, how errors surface for an invalid ID, or whether subtasks are excluded by default. For a tool with zero annotation coverage this is a significant gap.

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?

A single six-word sentence with no filler and the key scoping phrase ('by its ID') front-loaded. It is efficient, though its brevity is closer to under-specification than to well-structured conciseness.

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 simple read tool with full schema coverage and no output schema, the parameter side is adequately handled by the schema. However, with no annotations and no return-value or default-behavior notes, the description leaves the agent guessing about what comes back and when to use it.

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 task_id, include_subtasks, and include_markdown_description are all documented in the schema itself. The description adds only 'by its ID', which restates the required parameter without new format or behavioral detail, so the 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 ('Get a task') plus the lookup key ('by its ID'), so the agent knows this is a single-item retrieval rather than a list. It does not, however, name or differentiate itself from close siblings like clickup_get_tasks, clickup_search_tasks, or clickup_get_task variants.

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?

There is no when-to-use guidance at all: nothing explains when to prefer this over clickup_get_tasks or clickup_search_tasks, nor any prerequisites such as needing a task ID from a prior search. The 'by its ID' phrasing weakly implies you must already have the ID, but no alternative is named.

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