outlook_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 disclosure burden. It implies a state mutation but says nothing about prerequisites (Outlook must be running/authorized), whether the change syncs to the server, or whether it is reversible. For a mutation tool with zero annotation coverage this is a substantial gap.

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 triggering condition is front-loaded, which is good structure. However the description ends mid-clause, so it is under-specified rather than genuinely concise — the reader is left with an unfinished instruction.

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 and no output schema, the description must supply all behavioral context, and it does not: it does not say how target emails are identified given zero parameters, what the return looks like, or what happens on failure. The truncated ending compounds the incompleteness.

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 tool takes no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The only caveat is that the truncated text hints at a read/unread mode choice that isn't represented in the schema.

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 ('marked as read, or as unread') scoped to the 'classic Outlook app on this PC', which implicitly separates it from the cloud-based m365_mark_email_read sibling. The sentence is truncated ('...or as unread with...'), so the full scope of the operation is never stated.

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 triggering condition, but there is no explicit exclusion or naming of m365_mark_email_read as the alternative for cloud mailboxes. The trailing fragment leaves the second mode (mark as unread) unexplained, so the agent must infer routing.

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