create_omnifocus_task

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It adds only 'on this Mac', which hints at a local-app dependency, but says nothing about required permissions, whether OmniFocus must be running, which list/project the task lands in, or what a failure looks like for a mutation operation.

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?

A single front-loaded sentence with no filler; the verb and target are the first two words. It is efficient, though the brevity shades into under-specification for a write tool.

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 mutation tool with no annotations, no output schema, and an empty input schema, one sentence is not enough. The agent cannot tell what it must supply, what state the tool changes, or what the return value is.

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?

Parameter count is zero and the schema is an empty object, so the usual baseline would be 4. However, the description offers no indication of how task content is supplied (title, due date, project, tags) for a create operation, leaving a real semantic hole that the description could have acknowledged.

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?

States a specific verb (Creates) and resource (a task) scoped to a named product (OmniFocus), so it is distinguishable from generic siblings like create_reminder or todo_create_task. It stops short of explicitly contrasting itself with those siblings, so no differentiation credit.

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?

There is no when-to-use guidance and no mention of alternatives, despite the sibling list containing several near-identical create tools (todo_create_task, todoist_create_task, create_reminder, create_calendar_event). The agent is left to infer which task backend to target.

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