saveGmailDraft

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

No annotations are provided, so the description must convey the tool's behavior. It explains the core action (creating a draft that can be edited later) and the reply option, but lacks details on authentication, permissions, rate limits, or what the response contains. The behavior is adequately described for basic use but lacks deeper transparency.

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 two sentences long, front-loads the verb and resource, and avoids unnecessary elaboration. Every phrase adds value, and the optional reply behavior is stated succinctly.

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 tool has 7 parameters, no output schema, and no annotations, the description is moderately complete. It covers the main purpose and the reply option, but omits the return format (e.g., draft ID), any prerequisites, and does not address possible side effects beyond saving a draft. It is adequate but leaves operational details unclear.

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 100%, and parameter descriptions in the schema are already detailed (e.g., threadId explains automatic Message-ID fetching). The tool description adds no additional parameter-level meaning beyond referring to the reply-to-thread capability, which is already reflected in the schema.

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 clearly states the verb ('Creates and saves') and resource ('a draft email in the user's Gmail account'), distinguishing it from the sibling tool sendGmailEmail by emphasizing the draft can be 'edited and sent later.' The optional reply-to-thread capability is also clearly mentioned.

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 implies appropriate use for saving drafts rather than sending immediately, and mentions the optional reply-to-thread context. However, it does not explicitly name sendGmailEmail as the alternative for immediate sending, nor does it state when not to use the tool.

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