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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the core safety profile is covered by structured metadata. However, the description adds no behavioral context beyond the name—it does not state whether deletion is permanent, what happens to the draft after deletion, or any permission requirements.

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 extremely short and front-loaded with the action and resource. There is zero filler, though the brevity contributes to the gaps noted in other dimensions rather than being a structural flaw in itself.

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?

Although annotations cover the destructive/idempotent safety profile and an output schema exists, the description is incomplete for a mutation tool: it omits permanence, draftId semantics, and when to choose this over sibling deletion or trash operations. An agent has to rely almost entirely on the tool name and schema.

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 50%: accountId is documented, but draftId has no description in the schema and the tool description adds no meaning about what a draft ID is or how to obtain it. The description 'Delete a draft' only implies the draftId parameter without explaining it.

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 clear verb ('Delete') and resource ('draft'), so an agent can immediately tell this is a removal operation for drafts. It does not explicitly differentiate itself from siblings like trash_emails, update_draft, or get_draft, but the purpose 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?

There is no guidance on when to use this versus alternatives such as trash_emails, update_draft, or get_draft. The description gives no prerequisites, no conditions, and no exclusions, leaving the agent to infer usage solely from the tool name.

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