delete-task

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

Annotations already declare destructiveHint and idempotentHint, but the description adds non-obvious semantics beyond them: repeated deletion succeeds when nothing owned by the caller matches, and success does not prove a task previously existed. The caller-scoped ownership constraint is also disclosed, which annotations cannot express.

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?

Front-loaded with the destructive action and its precondition, then routes to siblings. Dense but nearly all sentences earn their place; the get-tasks-list/COMPLETED sentence is the one that drifts furthest from the deletion task itself.

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?

With one parameter, full schema coverage, no output schema, and destructive/idempotent annotations, the definition closes the remaining gaps: what is destroyed, how to source the identifier, and how to interpret a success response. Nothing an agent needs before calling is missing.

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 coverage is 100% and the single todoUUID parameter already documents its origin from get-tasks-list, so the description largely repeats the schema. The only added value is the instruction to clarify the target when ambiguous, which is workflow guidance rather than parameter meaning.

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 with scope: "Permanently deletes a single task from the TODO feature." The single-task and permanence qualifiers distinguish it from update-task and from any bulk operations in the sibling list.

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?

Gives an explicit gate ("Use only when the user requests deletion or removal") and names the correct alternative for the adjacent intent: update-task with status DONE for completion, and get-tasks-list for completed-item queries. It even prescribes clarifying ambiguous targets before acting.

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