clickup_task_link

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

Describes the bidirectional nature, visibility in 'Linked tasks' panel, and that it returns an empty object on success. With no annotations, this covers the key behavioral aspects, though could mention if it overwrites existing links.

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 sentences with no wasted words. Front-loaded with the core purpose, then provides removal and alternative usage. Highly efficient.

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?

Tool has low complexity with 2 parameters and no output schema. Description mentions successful return type, explains bidirectional nature, and includes ID source instructions. Complete for the task.

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 has 100% coverage with descriptions. The description adds value by specifying how to obtain parameter values (from clickup_task_list) and clarifying visibility for links_to. This goes beyond repeating schema info.

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?

Clearly states the tool creates a bidirectional reference link between two tasks, emphasizing it is a non-blocking 'see also' relationship. Distinguishes from dependencies, providing a specific verb and resource.

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 tells when to use this tool versus alternatives: use clickup_task_unlink to remove, and for blocking relationships use clickup_task_add_dep. Provides clear guidance on alternative tools.

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