exchange_set_mailbox

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

With no annotations, the description carries the full burden of behavioral disclosure. It indicates mutation via 'Set', but does not explain side effects, whether unspecified properties are reset, permission requirements, or what response to expect. This is similar to other minimally-described mutation tools.

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 short sentence and front-loads the action. It is appropriately concise, though the vague 'etc.' reduces precision slightly.

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 a mutation operation with no annotations and no output schema, and the description provides only the broad action. It omits critical context like which mailbox is being modified, how quota values should be formatted, and whether this replaces all mailbox properties or only the specified ones.

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 coverage is 0%, so the description must compensate, but it only names one actual parameter (prohibitSendQuota) and mentions 'retention', which does not appear in the schema. It does not explain 'identity', 'issueWarningQuota', or 'customAttribute1', nor their expected formats such as quota values.

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 states a specific verb ('Set') and resource ('mailbox properties'), and names example properties. It distinguishes the tool from sibling get/list/create/remove tools through the verb 'set', though it does not explicitly contrast with exchange_create_mailbox.

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 this is for modifying properties on an existing mailbox, which is a clear usage context. However, it gives no explicit guidance on when not to use it, nor does it mention alternatives like exchange_create_mailbox for new mailboxes or exchange_get_mailbox for reads.

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