set_conversation_mailboxes

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

No annotations are provided, so the description carries the full burden. The word 'replace' explicitly communicates destructive overwriting of the current mailbox set, which is a meaningful behavioral trait. However, it does not disclose permissions, reversibility, or side effects beyond the replacement.

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, clear sentence with no verbose or redundant content. It is appropriately front-loaded and easy to scan.

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?

The tool is relatively simple, and an output schema exists so return values need not be described. The description conveys the core action ('replace the set'), which is essential. However, it lacks broader context such as when to use this compared to other conversation actions, and it does not clarify behaviors like whether the conversation or mailboxes must pre-exist.

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 0%, yet the description adds no parameter details. It implicitly connects 'mailboxes' to mailbox_ids and 'conversation' to conversation_id, but it doesn't explain how to use the parameters, their constraints, or the api_token field. The schema alone carries all parameter information.

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 uses a specific verb ('Replace') and clearly identifies the resource ('the set of mailboxes a conversation belongs to'). It distinguishes this tool from siblings like assign_conversation or archive_conversation, which operate on different aspects of a 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?

There is no guidance on when to use this tool versus alternatives. It simply states the action without mentioning exclusions, prerequisites, or comparing to other conversation/mailbox tools.

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