delete_task

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

No annotations are provided, so the description carries full burden. It discloses permanent deletion, destructiveness, the confirm requirement, and the return payload. This is good behavioral transparency beyond the schema, though it doesn't mention cascading effects on related data.

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?

Two sentences, front-loaded with purpose, then caution, then return value. Every word is necessary; no redundancy or fluff. Highly concise and well-structured.

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 delete operation with only two parameters, full schema coverage, and no output schema required beyond the stated return, the description provides all necessary context: what it does, how to use it (with confirm), and what to expect back. No missing critical information.

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 input schema has 100% coverage with descriptions for both parameters. The description does not add new semantic information about the parameters beyond what the schema provides. It reinforces the confirm requirement but no new details, so baseline score 3 is appropriate.

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 'Permanently delete a Kanboard task,' which is a specific verb+resource. Among sibling tools like delete_column and delete_subtask, it uniquely identifies the tool's action. The return value is also mentioned, adding clarity.

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 explicitly warns 'DESTRUCTIVE' and mandates 'requires explicit confirm: true,' guiding the agent to use it only when certain. It lacks explicit when-not-to-use or alternatives, but the caution is clear enough for safe usage.

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