batch_add_items

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

With no annotations, the description carries the full burden. It discloses only the max limit and batch nature, but omits critical behavior such as partial-failure handling, atomicity, validation rules, or output structure. For a mutation tool, this is insufficient.

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 one concise sentence, front-loaded with the action, and includes the important max-100 limit. It is efficient and well-structured, though it sacrifices completeness for brevity.

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 complexity (array of arbitrary objects), a schema with no property definitions, and the absence of annotations, this description is far too sparse. It does not explain the item format, expected fields, or behavioral outcomes, making it insufficient for correct invocation.

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 schema has one parameter with additionalProperties true and zero property definitions (0% schema coverage). The description only mentions 'tasks or projects' but fails to specify how each item should be structured, what fields are required, or how to differentiate between a task and a project.

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 a specific action ('Add'), the resource ('multiple tasks or projects'), and a key constraint ('max 100'). It effectively differentiates from singular tools like add_omnifocus_task and add_project, making its purpose unmistakable.

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 phrase 'in a single operation' implies use when batching multiple items, providing clear context. No explicit alternatives are named, but the sibling tools indicate singular options, so the usage is reasonably clear. However, it lacks explicit 'when not to use' guidance.

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