Mark email as unread

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

Annotations already indicate non-destructive write (readOnlyHint=false, destructiveHint=false). Description adds the flag-clearing detail, but lacks behavioral context such as permissions, side effects, or behavior on already-unread emails.

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?

Very concise single sentence that conveys the core purpose. Could be expanded slightly to include parameter defaults or usage hints without losing conciseness.

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?

Given the tool has three parameters and siblings, the description is too minimal. It omits crucial context like how to obtain the uid, the effect of default folder/server, and what happens if the email is already unread.

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 description does not discuss any of the three parameters. With only 33% schema coverage and no parameter descriptions in the text, the agent must rely solely on the schema, which lacks descriptions for uid and folder.

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?

Description clearly states the action (mark as unread) and the underlying mechanism (clears \Seen flag). It implicitly distinguishes from email_mark_read, though it could explicitly contrast with email_flag or similar.

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?

No usage guidance provided. The description does not indicate when to use this tool over email_mark_read, email_flag, or other siblings, nor mention prerequisites like needing the UID.

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