Create many tasks

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

Annotations already provide idempotentHint=true and destructiveHint=false. The description adds crucial behavioral detail: skipIfExists default matching rule (title AND due match existing open task), and that the response is a per-item report requiring checks for partial failures. This goes well beyond annotations.

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?

Three concise sentences deliver the core purpose, key parameter semantics, and error-handling guidance. No filler or redundant repetition of schema fields.

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 bulk-create complexity, the description covers list default, item fields, idempotency, and partial-failure reporting. Even without an output schema, the agent knows what to expect and how to handle errors. The description is sufficiently complete for safe 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?

Schema description coverage is low (33%), so the description must compensate. It explains the due format as all-day, the default skipIfExists=true, and the safe retry semantics. It does not cover parentTaskId, but the schema does describe it. Overall it adds meaningful meaning beyond the 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 opens with 'Create up to 100 tasks in one call', which is a specific verb+resource+capacity statement. The example 'e.g. every reading from a syllabus' and the bulk nature clearly distinguish this from the sibling create_task (singular).

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 use for bulk creation ('up to 100 tasks', 'every reading from a syllabus') and explains idempotent retry behavior with skipIfExists. It does not explicitly mention when not to use this vs create_task, but the 'one call' contrast and sibling names provide sufficient context.

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