task_batch_create_describe

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

Explicitly declares no side effects, read-only by contract, never mutates OmniFocus. Also describes return value shape { description, plannedChanges }.

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?

Two sentences plus an example; front-loaded with purpose and guidance. Every sentence earns its place with 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?

For a simple dry-run tool with 2 params and no output schema, the description covers all needed: return value, safety, workflow, and idempotency key in schema. Completely adequate.

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 detailed descriptions; description does not add extra parameter info. Baseline 3 is appropriate as description focuses on tool purpose rather than parameters.

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 it previews what task_batch_create would do without changes, using specific verb 'preview' and resource 'task batch creation'. It distinguishes from sibling by warning not to create tasks.

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 tells when NOT to use (actual creation) and provides alternative (task_batch_create). Gives clear workflow: pass same args, inspect plannedChanges, then call write tool.

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