outlook_get_mail_tips

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

readOnlyHint=true already tells the agent this is a safe, non-mutating call, so the bar is lower. The description adds real value by naming the categories of information returned, which compensates somewhat for the missing output schema, but it says nothing about behavior with invalid addresses, maximum recipient count, or partial/empty results.

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 front-loaded clause with zero filler; the core purpose and the returned tip categories both land immediately. It reads as a fragment rather than a sentence, but nothing is wasted.

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?

For a one-parameter, low-complexity read tool this covers the essentials, and with no output schema the tip-category list usefully sketches what comes back. It still leaves the agent guessing about result structure and edge cases, so it is adequate rather than complete.

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?

Schema coverage is 0% for the single required parameter, so the description must carry the load. "Recipients" loosely implies the array holds email addresses, but it never confirms the expected format (SMTP address vs. UPN vs. display name), accepted count limits, or duplicate handling.

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 states a specific operation (a pre-send check) on a specific resource (recipients) and enumerates the tip categories returned (out-of-office, delivery limits, mailbox-full). It is clearly distinct from sibling send tools such as outlook_send_message or outlook_reply, though it never names a sibling explicitly.

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?

"Pre-send check" implies the usage context — call this before sending — but the description never states that explicitly, never names outlook_send_message/outlook_reply as the tools it precedes, and gives no when-not-to-use guidance (e.g., for internal-only batches).

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