create_forward_draft

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

Annotations only provide destructiveHint=false. Description adds that it pre-fills original message as quoted body and returns a draftId. Could mention more about saving to drafts or potential side effects, but overall adequate given no contradictions.

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 sentences, front-loaded with purpose and usage. No fluff, every sentence adds value. Highly concise and well structured.

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?

With 9 parameters (2 required) and no output schema, the description covers the main workflow: creating a draft for forwarding and returning a draftId. Could mention optional attachments handling, but overall complete enough for an AI agent.

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 baseline is 3. Description reinforces the purpose of emailId and to as required, but adds no new parametric details beyond schema. Adequate but not exceptional.

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?

Description clearly states it creates a forward draft for an existing email, pre-filling the original as quoted body. Distinguishes from siblings like forward_email (send immediately) and send_draft (send later). Verb 'create' and resource 'forward draft' are specific and accurate.

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?

Explicitly says when to use: when you have an emailId and want to stage a forward for review. Recommends alternative (forward_email) for immediate sending. Also mentions return of draftId for later update/send. Provides clear context and exclusions.

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