update-mailbox-settings

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

Annotations indicate readOnlyHint=false (mutation allowed) and destructiveHint=true (potentially destructive). The description's 'configure or disable' aligns with this. No contradictions, but the description adds limited extra behavioral context beyond what annotations already convey.

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 structured with a purpose statement followed by tips and an example. It is reasonably concise but includes some redundancy (e.g., the tip repeats the purpose). The example is helpful but makes it slightly longer than necessary.

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?

Given the complexity of mailbox settings (nested objects, multiple fields), the description covers the out-of-office use case well but omits guidance on other settings like working hours, language, or delegate meeting messages. Without an output schema, more detail on return behavior would be beneficial.

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?

The description adds value beyond the schema by explaining format requirements (short date, short time, time zone formats) and providing a body example for automaticRepliesSetting. However, other sub-properties (working hours, language) are not elaborated.

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 the tool updates mailbox settings (enable, configure, disable) and provides examples. It distinguishes from sibling tools which act on other resources (calendars, emails, etc.), but does not explicitly differentiate from similar update tools.

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 gives tips on date/time format and time zone format, and provides a common use case (out-of-office). However, it lacks explicit guidance on when to use this tool versus alternatives or when not to use it.

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