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

Annotations already disclose a non-read-only, destructive mutation, and the description adds nothing beyond restating the fields, so the agent learns nothing about whether marking read is reversible, what 'outcome' values exist, or what permissions are needed. For a destructiveHint=true tool, the unclear semantics of 'outcome' is a real gap the description should have closed.

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?

A single compact sentence with the operation front-loaded and no filler. It is efficient, though the leading title repetition is mild redundancy.

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?

An output schema exists, so return values needn't be explained, and the four params are covered by the schema. Still, the loosely defined 'outcome' field and the absence of any note on scope or side effects leave the agent under-informed for a destructive mutation.

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%, so messageId, unread, outcome, and workspace_id are already fully documented; the description only repeats the unread/outcome operations. It does not clarify what valid 'outcome' strings are or whether both fields can be set in one call, so baseline 3 is appropriate.

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?

"Mark emails as read/unread or update outcome" states a specific verb and resource with the two supported field operations, so an agent knows exactly what it mutates. It loses the top score only because it largely echoes the title and gives no signal for separating it from siblings like update_lead or forward_inbox_message.

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 names the operations but never says when to reach for this tool versus alternatives such as forward_inbox_message or send_reply, and gives no prerequisites (e.g., whether the message must belong to the selected workspace). Usage is only inferable from the verb.

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