m365_mark_email_read

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

No annotations are provided, so the description carries the full behavioral burden and largely drops it. It does not say which emails are affected, whether the change is applied server-side and syncs back, whether it requires specific mail permissions, or that calling twice is idempotent. The text is also truncated mid-clause ("as unread w..."), which leaves the unread-branch behavior unresolved.

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 trigger condition is correctly front-loaded, which is the right structure. However the definition is cut off mid-word, so the second half of the behavioral scope (marking as unread) is never actually delivered — that is under-specification masquerading as brevity.

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?

This is a mutation tool with no annotations, no output schema, and no parameters, and the description does not compensate for any of those gaps. An agent would not know what scope of mail is modified, what permissions are needed, or what is returned after the state change.

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 input schema declares zero properties, so there are no parameters for the description to explain; the baseline for a 0-parameter tool applies. The notable concern is not parameter prose but that a zero-argument tool cannot express which emails to mark, and the description does not clarify that gap.

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 concrete verb+resource pair ("emails ... marked as read, or as unread") scoped to Microsoft 365 / Outlook, which is far more than a restatement of the name. It does not, however, differentiate itself from the near-identical sibling outlook_mark_email_read, so an agent cannot tell which of the two to pick.

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?

"Use this when the user wants..." gives a real trigger condition, which is better than nothing. But it gives no when-not condition, no prerequisites (signed-in account, which message set), and no routing rule versus the duplicate outlook_mark_email_read sibling.

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