clickup_task_remove_dep

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

Discloses that tasks are not affected and returns an empty object on success. No annotations to contradict. Lacks description of error cases or idempotency, but reasonable for no 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?

Three concise, front-loaded sentences covering action, usage direction, behavioral note, and return value. No fluff.

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 removal tool with no output schema, description covers all essential aspects: parameters, usage rule, task safety, and return value. Agent can effectively invoke 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?

Adds value beyond schema by explaining mutual exclusivity of depends_on and dependency_of, and how they relate to the add operation. Provides context for task_id derivation from other tools.

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 it removes a dependency relationship between two tasks, with a specific verb and resource. References sibling tool clickup_task_add_dep for direction context.

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 instructs to provide exactly one of depends_on or dependency_of, matching the direction from the add operation. Implicitly advises against using both. Could mention when not to use, but adequate.

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