outlook_read_email

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

No annotations are provided, so the description must carry the full behavioral burden. It only states that it reads full content; it does not mention side effects (e.g., marking as read), required permissions, or output format.

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 a single, front-loaded sentence with no wasted words. It is appropriately sized for the tool's apparent simplicity.

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 empty schema, lack of annotations, and no output schema, the description is missing critical details: how to provide the EntryID when the schema has no parameters, and what the returned content looks like. It is too sparse to confidently invoke the tool.

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 has zero parameters, but the description references an EntryID, creating an inconsistency. This adds semantic meaning about the identifier but does so in a way that contradicts the empty schema, leaving the agent unable to supply the required input.

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 specific verb (reads), resource (Outlook email), and scope (full content) with the lookup method (by EntryID). It is clear what the tool does, but it does not explicitly differentiate itself from sibling tools like m365_read_email or read_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 implies usage requires an EntryID, but gives no explicit guidance on when to choose this tool over alternatives such as outlook_list_emails or outlook_search_emails. There are no stated prerequisites or exclusions.

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