Batch Update Conversations

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

Annotations already flag destructiveHint=true and idempotentHint=false; the description adds real value by calling out irreversibility and mandating a preview-then-confirm sequence, plus scope ('only your own inbox'). It stops short of saying whether the dry-run returns per-conversation results or what happens to partially invalid IDs.

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 tight sentences, front-loaded with purpose and scope, then the safety-critical confirm instruction flagged in brackets. No wasted text.

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 destructive batch mutation with no output schema, it covers scope, action set, and the confirm gate. The only gap is what the dry-run preview returns, which the agent must infer.

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% and already documents event, confirm, and conversation_ids thoroughly. The description only reiterates 'one action' and the confirm protocol, adding little beyond the schema baseline.

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?

States a specific verb (apply one action) and resource (Inbox conversations), enumerates the actions, and makes batch scope explicit with 'to many ... at once', which distinguishes it from the single-conversation siblings like mark_conversation_read and delete_conversation.

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?

Clear on context ('Only affects your own inbox') and lays out the required confirm-first workflow. It never names a single-conversation sibling as the alternative when only one ID is involved, so guidance is strong but not exhaustive.

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