delete_task

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. It only says 'Delete a task' without stating whether the deletion is permanent, cascading, requires permissions, or has side effects on related entities like tags or dependency views. This is a significant gap for a destructive operation.

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, front-loaded sentence with no unnecessary words. It communicates the essential action and parameters efficiently, earning its place without padding.

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 is a simple deletion tool with two parameters and no output schema or annotations. However, the description omits critical context: it doesn't explain return values, error scenarios, whether deletion is permanent or reversible, or any relationships to other resources. Given the destructive nature, the description should provide more safety-related details.

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 description adds meaning to the parameters by indicating that 'project ID' and 'task ID' are the identifiers used to locate the task. Since schema_description_coverage is 0%, this partial explanation is helpful, but it doesn't provide further context such as where to find these IDs or any constraints beyond the schema's minLength.

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's function with a specific verb ('Delete') and resource ('a task'), and identifies the two identifiers needed (project ID and task ID). This distinguishes it from sibling tools like get_task, update_task, and batch_update_tasks, which have different purposes.

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 no guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or situations where a different tool (e.g., batch update or dependency view removal) might be more appropriate. The agent is left to infer usage solely from the tool name and description.

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