zoho_delete_email

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

Annotations already declare destructiveHint=true, but the description adds the crucial nuance that the DEFAULT is recoverable (moved to Trash) and that permanent deletion is gated behind a server flag. This reversibility and prerequisite information materially changes how an agent should treat the call and is not derivable from annotations alone.

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?

Three short sentences with zero padding; the default behavior is front-loaded before the opt-in destructive path. Every sentence carries information an agent needs.

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 3-parameter mutation tool with no output schema and full schema coverage, the description covers the essential behavioral contract: default recoverability, the permanent-delete flag, and its environment prerequisite. It could note the failure mode when expunge is requested without the server flag, but the 'only works when' phrasing already implies it.

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?

Schema coverage is 100%, so the baseline is 3. The description goes beyond the schema's terse 'Permanently delete instead of moving to Trash' by disclosing that expunge only functions when the server runs with ZOHO_ALLOW_PERMANENT_DELETE=true, a runtime precondition the schema does not mention.

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 and resource ('Delete an email') and immediately scopes the operation by distinguishing soft delete (Trash, recoverable) from permanent delete. This differentiates it from siblings like zoho_move_emails and zoho_archive_emails without the agent needing to open another schema.

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 description explains the two modes of this tool, but gives no explicit guidance on when to choose deletion over alternatives such as zoho_archive_emails or zoho_move_emails. Usage is implied by the tool name rather than stated, leaving the routing decision to inference.

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