outlook_send_email

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

No annotations are provided, so the description carries full behavioral burden. It says only that an email is sent via Outlook on Windows, without disclosing immediacy, account/auth requirements, attachment behavior, or any side effects for a mutation operation.

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?

A single clear sentence with the verb and resource front-loaded and no wasted wording. It is appropriately concise, though its brevity leaves important behavior and usage details unaddressed.

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, no output schema, and an empty input schema, the description is too thin for an email-sending tool. It does not explain how message content is supplied or how this differs from other send-email siblings.

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 has zero parameters, so the baseline is 4. The description adds no parameter semantics, but no parameters are declared in the schema; the omission of expected email fields like recipient, subject, and body is notable but outside parameter coverage.

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 and resource, 'Sends an email,' plus the platform context 'via Microsoft Outlook on Windows.' However, it does not distinguish this tool from sibling send tools such as send_email, m365_send_email, or zalo_send_message.

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?

Provides no guidance on when to use this tool instead of send_email, m365_send_email, or other messaging siblings. It also omits prerequisites such as requiring a configured Outlook account on Windows.

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