delete_email

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

Description discloses the behavior of the permanent parameter (hard delete vs move to deleted items). However, no annotations exist, and the description does not cover other behavioral traits such as authentication requirements, error handling, or idempotency.

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 very concise: a one-line purpose followed by a short Args section. Every sentence adds value with no redundancy.

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 simplicity of the tool (delete with two params) and presence of an output schema, the description covers the core behavior adequately. It explains the permanent flag. Lacks details on error handling or edge cases but is acceptable.

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?

With 0% schema description coverage, the description compensates by explaining item_ids as 'List of Exchange ItemIds' and permanent. Adds meaning beyond the schema. Could include more detail on valid ItemIds.

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 'Delete one or more emails' clearly states the action and resource, distinguishing it from siblings like move_email and empty_folder.

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?

Describes behavior of the permanent parameter but does not provide explicit guidance on when to use this tool vs alternatives like move_email or empty_folder. Context is implied but not stated.

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