Delete a task

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

With no annotations, the description must disclose behavioral traits itself. It clearly communicates that deletion is destructive and irreversible, which is the most critical behavior. However, it does not describe side effects, return values, error conditions, or permission requirements, leaving some burden unmet.

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?

The description is extremely concise and front-loaded, containing only the essential information: the action, the target, and the irreversibility. Every word earns its place and there is no filler.

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?

For a simple one-parameter deletion tool, the description is minimally usable and conveys the core semantics. However, with no output schema and no usage guidance, the agent is left without information about expected return behavior or edge cases, so it is not fully 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?

The schema has one required 'id' parameter and 0% schema description coverage, so the description should compensate. It does not explain the id format, scope, or relationship to the task being deleted, though the id's general purpose is inferable from context.

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 states a specific verb ('Deletes') and resource ('a task'), and the modifier 'irreversibly' clearly distinguishes this from sibling tools like sp_task_archive and sp_task_restore. An agent can understand exactly what this tool does from one sentence.

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 description gives no guidance on when to use this tool versus alternatives. Notably, it does not mention that sp_task_archive may be preferable when reversible deletion is desired, despite the sibling tools making that distinction relevant.

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