Mark several emails as unread in one batch using their UIDs, so you can restore unread status across multiple messages in a folder at once.
Mark multiple emails as unread using their UIDs. Batch operation for efficiently updating unread status of several emails at once.
| Name | Required | Description | Default |
|---|---|---|---|
| uids | Yes | ||
| folder | No | INBOX |
Changes observed during successful MCP inspections.
v1.0.9Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description bears full burden. It says 'batch operation' and 'efficiently updating', but does not disclose whether changes are reversible, whether UIDs must be valid, error behavior for partial failures, or permission requirements. Minimal behavioral context.
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?
Two concise sentences, front-loaded with the action and mechanism. No wasted words, though it repeats 'unread' and 'batch' without adding new information.
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?
With no annotations, no output schema, and 0% parameter description coverage, the description omits critical operational details: how UIDs map to emails, what happens if a UID is invalid, whether the operation is atomic, and how the folder parameter affects scope. Incomplete for a mutation tool.
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 0%, so the description must compensate. It mentions 'using their UIDs' and implies a folder context but does not explain that 'uids' is an array of numbers or that 'folder' defaults to INBOX. The schema names the parameters but lacks descriptions, and the description adds no format or default details.
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?
States a specific verb (mark) and resource (emails as unread) and specifies batch scope via UIDs. Distinguishes from single-item sibling markAsUnread implicitly through 'multiple' and 'batch', though it doesn't explicitly name the sibling.
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?
Implies use when updating multiple emails at once, but gives no explicit when-to-use versus markAsUnread or markMultipleAsRead, no preconditions (e.g., folder must exist or default to INBOX).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.