delete_task_dependency

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

With no annotations provided, the description carries the full burden of behavioral disclosure. The description only states the action without revealing what happens to related data, whether the operation is reversible, what the effect is on task scheduling/critical paths, or how the directionality of the dependency removal works. For a mutation tool with zero annotation coverage, this is a notable 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?

The description is a single, efficient sentence with zero waste. This is appropriately concise—though concise to the point of underspecification, the structural economy itself is admirable.

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?

This tool has 3 parameters (one required), no output schema, and no annotations. The description is a single sentence that fails to explain the directional semantics of dependencies, the meaning of two of the three parameters, or what the expected return value is. For a mutation tool with this complexity, the description is significantly under-equipped to guide correct invocation.

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 only 33% with 3 total parameters, so the description must compensate. Only task_id is documented in the schema ('The task ID'), while depends_on and dependency_of have no schema descriptions and no explanation in the tool description. The key semantic ambiguity—whether the dependency is incoming or outgoing—is entirely unresolved, making it impossible to correctly invoke this tool.

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 'Remove a dependency between tasks' uses a clear verb+resource construction that states the core purpose. However, it doesn't explain the directionality of dependencies (which task depends on which), which is the main ambiguity here given the depends_on and dependency_of parameters. It doesn't distinguish itself from the sibling add_task_dependency beyond being the inverse operation.

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 is provided on when to use this tool versus alternatives, and critically, there's no explanation of the semantic difference between depends_on and dependency_of. The agent can't determine whether to remove a dependency where this task depends on another, or where another depends on this task. No context about prerequisites or when dependency removal is appropriate is given.

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