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

Annotations already flag a non-read-only, non-idempotent mutation, so the safety profile is covered. The description adds mode semantics and the 2+ constraint, but omits what switching does to existing mailboxes, warm-up state, or whether the change is reversible.

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?

A single compact sentence with the default mode front-loaded. The parenthetical style is efficient, though slightly fragmentary and reliant on the tool name for the action.

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 simple boolean setting with annotations present, the key option meanings and default are covered. It leaves ambiguous whether the setting is account-wide or workspace-scoped and what immediate effect toggling has on current mailboxes.

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% for the sole private_pool boolean, but the description effectively maps the false/default case to shared network and the true case to private pool with a 2+ mailbox requirement.

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?

Defines the two pool modes and the default, making the setting's purpose inferable alongside the name set_pool_mode. However, it never explicitly states that this tool changes the mode or what entity the setting applies to.

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?

It gives the default shared mode and a prerequisite (2+ mailboxes for private pool), which implies when private mode is appropriate. But it provides no explicit when-to-use/when-not guidance or named alternatives.

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