combell_mailboxes_set_auto_reply

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe, idempotent write operation. The description adds the semantic context that this configures the out-of-office auto-reply, which is useful. However, it doesn't disclose any additional behavioral traits such as whether enabling auto-reply without a message is valid, whether existing settings are overwritten, or any side effects on other mailbox settings. With annotations covering the safety profile, a 3 is appropriate.

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, concise sentence that front-loads the verb and resource. It earns its place by clarifying the domain-specific term 'auto-reply' with the parenthetical '(out of office)', which aids an agent's understanding. No wasted words, though it could have added a bit more context without becoming verbose.

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 configuration tool with 4 parameters, no output schema, and annotations covering idempotency and safety, the description is adequate but not complete. It doesn't explain the relationship between 'enabled' and the optional 'message'/'subject' parameters (e.g., whether message/subject are required when enabled=true), nor does it mention any validation rules. An agent could call the tool correctly with the schema, but edge cases around the auto-reply content are left ambiguous.

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 50%: the 'message' and 'subject' parameters have descriptions, while 'mailbox_name' and 'enabled' do not. The description adds no parameter-level detail beyond what the schema already provides. The tool description does clarify the overall purpose (auto-reply configuration), which helps interpret the parameters, but it doesn't compensate for the undocumented 'mailbox_name' and 'enabled' fields. Baseline 3 is appropriate since the schema covers half the parameters and the description adds minimal extra meaning.

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 ('auto-reply (out of office) of a mailbox'), which clearly identifies the tool's function. It distinguishes it from sibling tools like combell_mailboxes_set_auto_forward and combell_mailboxes_set_password by naming the specific feature being configured, though it doesn't explicitly contrast with those siblings.

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 the tool is used when a mailbox's auto-reply/out-of-office settings need to be changed, but it provides no explicit guidance on when to use this tool versus alternatives like combell_mailboxes_set_auto_forward or combell_mailboxes_set_password. The context is clear enough for an agent to infer the use case, but there are no exclusions or alternative routing.

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