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

With no annotations, the description carries the full burden and does a decent job: it discloses mailbox-wide blast radius ('on a box held by several people it moves the thread for all of them'), the reversal behavior ('comes back to the Inbox when a new message arrives'), and a rejection case for queues. It omits permissions needed and what the call returns, which keeps it below 5.

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?

Four sentences with real content, but the lead sentence is long and indirect ('Says whether a thread of a mailbox leaves the Inbox for the Archive as soon as the box answers it'), burying the action behind a definition of the setting. Front-loading the operation would earn a higher score.

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 two-parameter boolean toggle with no output schema and no annotations, the description covers the semantics, the blast radius, the reversal condition, and an inapplicable case. Only permissions and return behavior are unaddressed, which is a minor gap at this complexity.

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 100% and both parameters are documented in-schema, including that address comes from list_sender_addresses. The description adds conceptual context about what the boolean governs but no syntax or format detail beyond the schema, so baseline 3 applies.

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 resource is identifiable as the mailbox-level 'archive on reply' setting, but the opening phrase 'Says whether...' frames it like a query rather than a mutation, and the word 'set' only appears in the tool name. An agent must infer that this writes a boolean setting rather than reading one.

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 concrete scope conditions: it applies to shared boxes and moves the thread for every holder, while 'A helpdesk queue refuses it, its threads being worked by status' is an explicit when-not-to-use rule. It does not, however, point to any sibling settings tool (e.g. set_auto_draft) as an alternative.

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