todo_delete_task

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety bar is low, but the description still adds real value: 'Permanently' signals irreversibility and the confirmation requirement is an operational constraint absent from the structured data. It stops short of saying what collateral is removed (checklist items, attachments) or whether auth/sign-in is required.

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, zero filler, with the destructive nature and the confirmation gate front-loaded. Nothing to cut.

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?

Annotations carry the safety profile and there is no output schema to explain, so the main remaining need is identifier semantics and deletion scope. Both are missing at 0% schema coverage, making this only minimally adequate for an irreversible 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% and both parameters (list_ref, task_id) are required. The description says nothing about what a list_ref is (id vs display name), nor that task_id must belong to that list, leaving the agent to guess at identifiers.

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?

Specific verb plus resource ('Permanently delete a To Do task') tells an agent exactly what happens. The 'To Do' naming implicitly separates it from the Planner siblings (planner_delete_task), but the description itself never draws that distinction explicitly.

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 only guidance is 'Confirm with the user first', which is a safety instruction rather than a when-to-use rule. It does not say when to delete versus archive/update, nor redirect to a sibling such as todo_update_task when the user may only want to close the item.

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