outlook_send_draft

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the agent knows this is a mutating, irreversible action. The description adds the human-review flow context, which is mildly useful, but says nothing about what happens to the draft after sending (removal, move to Sent) or delivery side effects.

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?

One short sentence, front-loaded with the action and resource, with the workflow hint trailing. No wasted words.

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 single-parameter, no-output-schema tool with safety annotations already present, the essentials are covered. Missing: sourcing of draft_id and the post-send disposition of the draft, which would make it fully self-sufficient.

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?

Only one parameter exists and schema coverage is 0%, so the schema itself says nothing about draft_id. The description also omits where draft_id comes from (create_draft or list_drafts), leaving the agent to infer it; the parameter name is largely self-explanatory, so this is a moderate gap rather than a severe one.

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 ('Send') and resource ('an existing draft'), which cleanly separates it from outlook_create_draft (makes the draft) and outlook_send_message (composes and sends directly). Clear purpose, though it doesn't explicitly name those siblings as alternatives.

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 parenthetical 'pair with outlook_create_draft for human-review send flow' implies the intended workflow and hints at when this tool is appropriate. It does not state when to prefer it over outlook_send_message, nor any prerequisite that the draft must already exist.

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