m365_create_draft

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

With no annotations, the description must carry the behavioral load. It does disclose the single most important trait — the message is not sent — but the description is truncated and says nothing about where the draft is stored (Drafts folder), whether it can be edited/reused, or what auth/account state is required.

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 definition is a sentence fragment ending in a colon and an ellipsis, so it is under-specified rather than concise. There is no front-loaded statement of what gets created or how, and the reader is left waiting for content that never arrives.

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 zero-parameter, no-output-schema, no-annotation creation tool, the description is the only place an agent can learn where the draft lands and how content is specified. It is truncated before delivering any of that, so it is not complete enough to call the tool confidently.

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 exposes zero properties, so there are no parameters to document and the baseline is 4. However, the dangling colon at the end suggests a content/specification list was intended and got cut, leaving an agent unsure how the draft body is supplied.

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 names a specific verb ('prepared'/'create draft') and resource ('email in Microsoft 365 / Outlook'), and its final clause 'without sending it' distinguishes it from the sibling m365_send_email. The trailing ellipsis means the statement of what the draft contains is cut off, but the tool's core identity is unmistakable.

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 an email prepared ... without sending it' gives an explicit positive trigger and implicitly excludes the send path, which maps to m365_send_email. What is missing is a named alternative for the sending case and any prerequisite (account connection, default account selection).

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