Set Mail Read State

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

With no annotations provided, the description carries the full burden. It discloses the mutating nature ('mark...read or unread') and the required permission (delegated Mail.ReadWrite), adding meaningful context beyond the schema. However, it does not describe any potential side effects or return behavior, leaving minor gaps.

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 concise and front-loaded: two essential sentences plus a useful Chinese intent mapping. Every sentence serves a purpose—function, permission, and multilingual intent—without fluff or repetition.

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's simplicity, the description covers the core action, permission, and parameters clearly. The absence of an output schema is acceptable for this mutation tool, though a brief note on the response could have added completeness. Overall, it is sufficiently complete for an agent to use correctly.

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 schema already documents both parameters (messageId and isRead) with clear descriptions, yielding 100% coverage. The tool description adds no additional parameter-level meaning, so it stays at the baseline of 3.

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 clearly states the tool's function with a specific verb and resource: 'Mark a message as read or unread.' This directly distinguishes it from sibling mail tools like mail_move_message or mail_delete_message. The Chinese intent mapping reinforces the purpose without ambiguity.

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 provides the prerequisite 'Requires delegated Mail.ReadWrite' but does not offer explicit when-to-use guidance or alternatives. There is no mention of when to prefer this over other mail operations, only implied usage from the action described.

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