outlook_delete_message

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

Discloses default soft delete vs hard-delete with permanent flag. No annotations provided, so description carries full burden; it covers the essential behavior but could mention auth requirements or reversibility.

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?

Two concise sentences front-loading key info: action, default behavior, alternative to avoid. No redundant text.

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 simple param set (2 params), no output schema, and no annotations, the description is fully adequate for correct tool invocation, covering behavior and usage constraints.

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?

Description explains the 'permanent' parameter but does not add meaning to 'message_id' beyond schema. With 0% schema description coverage, more detail on message_id (e.g., source or format) would improve clarity.

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?

Description clearly identifies the action as deleting a message, specifies the resource (message), and distinguishes it from a sibling tool (outlook_move_message) by explicitly stating not to use that for deletion.

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?

Explicitly states when to use this tool ('canonical way to delete a message') and when not to ('Do NOT use outlook_move_message...'), providing clear usage boundaries and an alternative.

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