batch_add_items

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

With no annotations provided, the description carries full burden but only states it's an add operation without disclosing behavioral traits like whether it's idempotent, requires specific permissions, returns confirmation details, or handles errors for partial failures in batch processing. It mentions the batch nature but lacks depth on how it behaves.

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, efficient sentence that front-loads the key action and benefit with zero wasted words. It's appropriately sized for the tool's complexity and gets straight to the point without unnecessary elaboration.

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 the tool's moderate complexity (batch mutation with nested objects) and no annotations or output schema, the description is adequate but incomplete. It covers the basic purpose but lacks details on behavioral aspects, error handling, or return values, which are important for a mutation tool with multiple items.

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 description mentions 'tasks or projects' and 'multiple items', which aligns with the 'items' array parameter in the schema. With 100% schema description coverage, the schema fully documents the parameter details, so the description adds minimal value beyond confirming the parameter's purpose without providing additional semantics or usage examples.

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 action ('Add multiple tasks or projects') and target system ('to OmniFocus'), with the specific benefit of 'in a single operation' distinguishing it from single-item tools. However, it doesn't explicitly differentiate from sibling tools like 'add_omnifocus_task' or 'add_project' beyond the batch aspect.

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?

The description implies usage when adding multiple items is needed, but provides no explicit guidance on when to use this versus alternatives like 'add_omnifocus_task' or 'add_project' for single items, or prerequisites for batch operations. The context is clear but lacks comparative or exclusionary details.

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