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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond them – it does not say whether the delete is permanent or moves to trash, nor any auth/account scoping requirement.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity comes partly from omitting information rather than from tight editing.

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 destructive, open-world mutation tool with two undocumented parameters and no output schema, the description leaves key questions open: which account the draft belongs to, whether deletion is reversible, and what happens to a non-existent draftId. Annotations cover the safety hint but not the operational context.

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 description coverage is 0% and neither draftId nor accountId is explained anywhere. The word 'draft' loosely implies a draftId, but the agent gets no information about whether accountId is required to scope the mailbox or what format identifiers take.

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 (Delete) and resource (mailbox draft), which cleanly separates it from create_draft, get_draft, and update_draft in the sibling list. It does not explicitly name or differentiate against siblings, but the action itself is 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 on when to use this versus update_draft (e.g., editing contents) or get_draft, and no preconditions such as whether the draft must exist or whether it is recoverable. The agent must infer the use case from the name alone.

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