planka_delete_task

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

With no annotations, the description bears full responsibility for behavioral disclosure. It states 'Delete' but does not mention any side effects, irreversibility, required permissions, or return behavior. This is insufficient for a destructive action.

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?

A single, brief sentence that efficiently conveys the core function with no extraneous words. It is well-structured and front-loaded.

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 description is too sparse for a delete tool with no output schema, no annotations, and many sibling tools. It does not cover prerequisites, effects, or output, leaving the agent underinformed for 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?

The only parameter, task_id, is described in the input schema as 'ID of the task to delete', which is clear. The tool description adds no extra context (e.g., where to obtain the ID). Despite the context indicating 0% schema coverage, the schema actually provides a description, so the description's contribution is minimal but acceptable.

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 'Delete a task from a card' clearly states the action (delete) and the target (task from a card). It effectively distinguishes this tool from sibling tools like planka_add_task and planka_update_task, though it could be more specific about the context (e.g., task as a checklist item).

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 vs alternatives such as planka_delete_card or planka_delete_label. The description lacks explicit context for selection, assuming the agent knows to use it only for deleting a task from a card.

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