Delete Task

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is largely covered. The description adds the irreversibility nuance ('cannot be undone'), which is mild added value, but says nothing about what removal cascades to, whether subtasks/comments go with it, or required permissions.

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 padding, with the core action and its irreversibility front-loaded. Nothing could be trimmed without losing information.

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?

An output schema exists, so return values need no explanation, and annotations carry the safety semantics. Still, for an irreversible mutation the description omits any permission or scope context and leaves both parameters unexplained, making it only minimally complete.

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?

Both task_id and project_id have 0% schema description coverage and the description supplies no meaning for either — notably why project_id is required alongside task_id. With two undocumented parameters and no compensating description text, this is a clear gap.

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 task') with the permanence qualifier, which is unambiguous against siblings like dida365_delete_project. It does not explicitly contrast with other task-mutating siblings such as dida365_complete_task or dida365_update_task, but the resource noun does most of the distinguishing work.

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 when-to-use guidance, no mention of prerequisites (task ownership, project membership), and no routing to alternatives such as completing a task instead of deleting it. The only usage signal is the implied finality of 'permanently'.

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