Delete an OmniFocus task

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

With no annotations, the description carries the burden of disclosing behavior. It explicitly states 'Permanently delete' (irreversibility) and 'op=delete transaction' (write operation). This provides valuable context beyond the schema, though it does not mention error behavior or side effects like cascading.

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 a single sentence that is front-loaded with the primary action and purpose. Every word contributes meaning; there is no filler or redundancy.

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 delete tool, the description covers the core purpose and a key behavioral trait (permanence). However, it omits any information about return values, error handling, or task existence checks, and with no output schema or annotations, some of this context would be helpful.

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 0% description coverage, so the description must compensate. It merely says 'by id', which restates the parameter name without adding format, type details, or how to obtain the id. This is minimal added value over the schema.

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 'Permanently delete a task by id' clearly states the action (delete), the resource (task), and the mechanism (by id). It also adds a specific implementation detail ('writes an op=delete transaction') that distinguishes this from sibling tools like of_complete_task and of_edit_task.

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 usage context is implied by the tool name and description—this is the tool for permanent deletion. However, there is no explicit guidance on when to prefer this over alternatives like of_complete_task (which might be used to mark a task done instead of deleting it).

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