mark_email_read

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

With no annotations provided, the description must disclose behavioral traits. It correctly identifies the operation as a state change (read/unread) and explains the boolean parameter. However, it doesn't mention authentication requirements, side effects, or any potential reversibility beyond the inherent toggling. Given the straightforward nature of the tool, this is adequate but not thorough.

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 extremely concise: two sentences plus a properly formatted argument list. The purpose is stated first, followed by parameter details. No irrelevant information is included.

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 low complexity of the tool and the presence of an output schema, the description is sufficiently complete. It covers the operation and parameter semantics. However, it could mention that the operation is immediate or provide a link to documentation for the ItemIds format.

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 adds significant meaning beyond the input schema: it explains that 'item_ids' is a list of Exchange ItemIds and that 'is_read' defaults to True for marking as read. This clarifies the format and default behavior, compensating for the schema's lack of description.

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 purpose: marking one or more emails as read or unread. The verb 'mark' and the resource 'emails' are specific, and the tool is well-differentiated from sibling tools like delete_email, move_email, or reply_email.

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 no guidance on when to use this tool versus alternatives (e.g., when to mark as read vs unread, or how to handle bulk operations). There is no mention of when not to use the tool or any prerequisites.

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