complete_omnifocus_task

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

No annotations are provided, so the description must convey behavioral traits. It states the action ('mark complete') but does not disclose side effects, permissions required, reversibility, or what task is affected (implicitly the currently selected one). This is insufficient for an agent to understand side effects.

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 concise sentence, which is appropriate for a simple tool. It is front-loaded with the verb and resource. However, it could include a brief note on the implicit target without significant bloat.

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 no parameters, no output schema, and a straightforward action, the description covers the basic purpose. However, it omits how the task is identified (context-dependent), which is a completeness gap for a tool that requires implicit context.

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 has no parameters (0 parameters, schema coverage 100%), so the description does not need to explain parameter meanings. However, it should clarify how the tool determines which task to complete (e.g., 'completes the currently selected task'), which is missing.

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 'Mark an OmniFocus task complete' clearly states the verb and resource, distinguishing it from siblings like 'complete_reminder' by specifying the task type. However, it lacks context on how the target task is identified, given the tool has no input parameters.

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?

No explicit guidance on when to use this tool versus alternatives such as 'complete_reminder'. The tool name implies it's for OmniFocus tasks, but no when-to-use or when-not-to-use instructions are provided.

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