Remove Dependency

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

Annotations already declare destructive and read-only false. The description adds that only explicit dependencies are removed, which is useful context, but does not describe side effects, reversibility, or behavior when the dependency doesn't exist.

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?

One sentence, efficient, front-loaded with verb and object. No unnecessary words.

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?

Despite having 5 parameters and no output schema, the description provides only a single sentence. It omits behavior for missing dependencies, workspace scope, and return values, leaving agents without enough context for a destructive operation.

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 0%, so the description must compensate. It clarifies direction ('waiting-on or blocking') and implies two task IDs, but leaves workspace_id and custom_task_ids unexplained and doesn't clarify which task_id plays which role in the dependency direction.

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 action (remove), the resource (explicit waiting-on or blocking dependency between two ClickUp Tasks), and distinguishes from siblings like add_dependency. The qualifier 'explicit' adds precision about scope.

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?

No guidance on when to use this tool versus alternatives (e.g., add_dependency, delete_task). It doesn't mention prerequisites, scenarios, or when not to use it.

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