update_bulk_tasks

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

No annotations are provided, so the description carries full burden. It discloses the batch limit (up to 100) and notes that it returns a per-task success/error report. However, it does not mention rate limits, authentication requirements, or behavior on partial failures, which are useful for an agent.

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 concise sentences front-loaded with the action and constraint (Apply same changes, up to 100, returns report). No wasted words.

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 tool with nested objects and 4 parameters (2 required), the description covers the core behavior and return value. Without an output schema, the mention of 'per-task success/error report' is adequate. Could elaborate on what the report looks like, but it's sufficiently complete for an agent.

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 100%, so baseline is 3. The description summarizes the types of field changes (status, priority, etc.) but does not add new semantic meaning beyond the schema's already detailed parameter descriptions.

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 applies the same field changes to many tasks at once (up to 100) and lists specific examples like status, priority, due date, and assignees. This distinguishes it from sibling tools like update_task (single task) and create_bulk_tasks (creating 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?

The description provides clear use cases: 'Use to mass-change status, priority, due date, or add/remove assignees across a batch of tasks.' It implies batch operations but could explicitly contrast with single-task tools like update_task for when not to use.

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