Edit an OmniFocus task

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

With no annotations provided, the description discloses important behavioral traits: partial updates (only provided fields change) and the mechanism to clear dates (clearDue/clearDefer). This goes beyond the schema and gives the agent actionable usage knowledge, though it doesn't describe error handling or return values.

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 sentences, no fluff. Provides the core behavior and two specific usage notes, all front-loaded.

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?

Given 9 parameters, no output schema, and no annotations, the description gives the essential behaviors but lacks information about the return value, potential errors, or the effect on existing fields when not provided. It's a succinct summary but leaves some gaps for a comprehensive understanding.

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 input schema describes only 2 of 9 parameters (due and defer). The description adds semantic context by explaining the clearDue/clearDefer flags and the overall partial-update behavior, but it doesn't elaborate on parameters like flagged, estimatedMinutes, or the meaning of id. Since schema coverage is low, the description only partially compensates.

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 uses the specific verb 'Edit' with the resource 'task' and clarifies that it edits 'fields'. This clearly distinguishes it from sibling tools like add_task, complete_task, and delete_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 description provides context that this is for editing existing tasks and explicitly states that only provided fields change, guiding partial-update usage. It also gives a specific instruction for using clearDue/clearDefer to remove dates, though it doesn't explicitly mention when to prefer this tool over alternatives.

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