combell_mailboxes_set_auto_forward

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

Annotations already provide idempotentHint=true and destructiveHint=false, covering safety. The description adds the 'optionally keeping a copy' behavior, but this mirrors the schema. It does not disclose what happens when enabled=false or whether existing forwarding settings are overwritten.

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?

One concise sentence with the action and resource front-loaded, no filler or redundant phrasing. Every clause earns its place.

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 description covers the core purpose but omits important behavioral details such as how to turn off forwarding (enabled=false) and whether email_addresses are required when enabled. Without an output schema, these gaps create some ambiguity, though annotations mitigate safety concerns.

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 schema describes copy_to_myself and email_addresses, but not mailbox_name or enabled. The description adds some meaning ('one or more addresses', optional copy), partially compensating for the 50% schema coverage, but leaves enabled and mailbox_name semantics unexplained.

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 ('Configure') and resource ('automatic forwarding of a mailbox'), and includes the optional copy-keeping behavior. This clearly differentiates it from sibling tools like combell_mailboxes_set_auto_reply.

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 when to use the tool—when automatic forwarding is needed—but does not explicitly mention alternatives or how to disable forwarding. There are no exclusions or when-not-to-use notes.

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