kanbn_delete_simple_task

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

With no annotations, the description must carry the full behavioral burden. 'Remove' implies a destructive mutation, but it does not disclose whether deletion is permanent, affects associated data, or requires a specific board state. No preconditions, side effects, or reversibility information is provided.

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 sentence that front-loads the action and object with no filler. It is concise and to the point, though it sacrifices useful details that are scored elsewhere.

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?

The tool sits in a large sibling set with several overlapping actions (delete_task, archive_task, remove_all), and the description does not explain what a 'simple task' is or how this removal differs from those alternatives. With no output schema and no annotations, the agent lacks critical context for correct selection and 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 100%, so the schema already documents 'path' and 'input' with clear meanings. The description adds no further semantic detail beyond the phrase 'simple task', which is not explained in relation to the 'input' parameter. Baseline 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 states a specific verb ('Remove') and resource ('simple task') with a location ('from the board'), clearly identifying the action. However, it does not differentiate from sibling tools like kanbn_delete_task or kanbn_archive_task, and 'remove' is a synonym for the name's 'delete', providing no new distinction.

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?

There is no guidance on when to use this tool over alternatives. The description does not mention kanbn_delete_task, kanbn_archive_task, or any criteria that select for 'simple' tasks, leaving the agent to infer the usage context from the name alone.

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