task_clear_waiting_on

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

Discloses idempotency, return shapes, side effects (writes tag+note, sets syncPending). Missing error cases, but given no annotations, this is thorough for a simple 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?

Concise, front-loaded, and each sentence adds value (core action, idempotency, alternatives, returns, side effects, example). No fluff.

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?

Covers purpose, returns, side effects, and idempotency. No output schema, but return shapes are described. Lacks error handling details, but sufficient for single-param tool.

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 coverage is 100% with good parameter description; the description adds an example but no additional semantic value beyond what schema provides. Baseline 3 applies.

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 tool clears waiting-on tracking from an OmniFocus task, specifying it strips a fenced block and removes a tag. This distinguishes it from siblings like task_delete and task_update.

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 (to clear waiting-on) and when not to (to delete task or remove unrelated tags), with named alternatives (task_delete, task_update).

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