planner_delete_task

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

With no annotations, the description carries full behavioral burden. It does add a genuinely useful disclosure – a required confirmation flow (confirm_code) when the task involves unregistered people – but omits whether deletion is permanent, what happens to checklist items/assignments, and what permissions are needed.

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 short sentences with the destructive action front-loaded and the exception condition second. The phrase 'see confirm_code' is slightly circular, but nothing is padded or wasted.

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 an irreversible mutation with zero annotation coverage and two undocumented parameters. The output schema covers return values, but the description still leaves out permanence, permission requirements, and the mechanics of confirm_code – significant gaps for a delete operation.

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 0%, so the description must compensate for both parameters. It references confirm_code but only by name ('see confirm_code'), without explaining where the code comes from, its format, or what happens if it is omitted; task_id is not addressed at all.

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?

States a specific verb and resource ('Delete a Planner task'), which is unambiguous on its own. It does not distinguish itself from nearby siblings such as todo_delete_task or planner_complete_task, so an agent must infer the Planner-vs-To Do distinction from the name alone.

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 statement of when to choose this over siblings like planner_complete_task or todo_delete_task. The only procedural guidance is the conditional note that tasks involving people who haven't signed up require the user's confirmation via confirm_code, which is a precondition rather than tool-selection guidance.

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