task_clear_repetition

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

Discloses that the task becomes one-time, returns updated task with null repetitionRule, and that mutations don't sync automatically, requiring sync_trigger for cross-device visibility.

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?

Concise with no fluff. Front-loaded with purpose, includes an example, and covers all essential aspects in a few sentences.

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 tool with one parameter and no output schema, the description covers purpose, behavior, result, side effects, and syncing adequately.

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?

Schema already describes id with pattern and description. Description adds value by telling the agent where to get the id ('Get from task_list or search_query'), which is helpful beyond 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 clearly states the verb 'Remove' and the resource 'repetition rule from an OmniFocus task'. It distinguishes from sibling task_set_repetition by explicitly naming it for setting/changing.

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?

Explicitly says when to use (remove repetition rule) and when not to (use task_set_repetition for setting/changing). Also provides syncing guidance.

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