Complete an OmniFocus task

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It mentions optional ISO 8601 time but does not explain prerequisites, idempotency, what happens to already completed tasks, or the response. This is insufficient for a mutation tool.

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, front-loaded sentence with no redundant filler. Every word contributes to the meaning.

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?

The tool has no annotations and no output schema, so the description must explain return behavior and edge cases. It omits what the response looks like, error conditions, and how the optional time affects completion. For a simple mutation tool, it is minimally viable but leaves significant gaps.

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?

With 0% schema description coverage, the description should compensate. It adds ISO 8601 format for the 'when' parameter, which is useful. However, it does not add any meaning for the 'id' parameter beyond its name, which is self-explanatory but not explicitly tied to task identification.

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 'Mark a task complete' with an optional time qualifier, using a specific verb and resource. This clearly distinguishes it from sibling tools like of_edit_task or of_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 implies use for completing tasks but provides no explicit when-to-use guidance or exclusions. It does not mention alternatives like of_edit_task or when not to use this tool, so guidance is merely implied.

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