clickup_task_get

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

The description indicates the tool returns a task object and includes many fields, but it does not disclose potential side effects, permission requirements, or rate limits. Since no annotations are provided, the description carries full burden but offers only basic read operation disclosure.

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?

The description is relatively concise with two sentences, but the first sentence is somewhat lengthy by listing many fields. It is well-organized and front-loaded with the core action, earning a 4.

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 lack of an output schema, the description fairly comprehensively lists the fields returned and directs users on how to obtain the required task ID. However, it could be more explicit about whether all data is always returned or if there are limits.

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?

The input schema already provides clear descriptions for both parameters (include_subtaks and task_id). The description adds no additional semantic value beyond the schema, so baseline score of 3 is appropriate.

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 fetches the full object of a single ClickUp task, listing many specific fields (name, description, status, etc.), and distinguishes it from sibling tools by directing users to clickup_task_list or clickup_task_search for finding task IDs.

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 description provides explicit guidance on when to use this tool (to get a single task) and mentions alternative tools for finding task IDs, though it does not elaborate on other circumstances or exclusions.

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