outlook_delete_draft

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

The description only states the deletion action without disclosing behavioral traits such as error handling on non-existent drafts, permanence, or side effects. With no annotations, this minimal info is insufficient for safe invocation.

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, clear sentence with no unnecessary words. It could be slightly more informative without losing conciseness, but it is appropriately short for a straightforward action.

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 simple input (one param) and no output schema, the description provides minimal context. Missing details like return value (void? confirmation?), error behavior, and typical use diminish its completeness for an agent.

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 one required parameter (draft_id) with no description. The tool description does not add any meaning, format, or source for the ID, leaving the parameter entirely opaque despite 0% schema 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?

The description clearly states the action ('Delete') and the resource ('draft message by ID'). Among siblings like outlook_delete_message and outlook_delete_contact, it specifically distinguishes the target as a draft, making the purpose unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., outlook_delete_message for non-drafts) or prerequisites (e.g., obtaining the draft ID). The description lacks context for appropriate usage.

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