update_email_draft

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

No annotations; description carries burden. Discloses preservation of unchanged fields, a key behavioral trait. Lacks details on permissions or concurrency, but adequate for a simple update tool.

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?

Concise with a one-line summary, usage hint, then clean parameter list. Every sentence adds value, no waste.

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?

Covers all 7 parameters with clear defaults and behavior. Mentions return value. Lacks preconditions (e.g., draft must exist) but acceptable for a simple tool with no output 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 coverage is 0%, but the description provides thorough parameter explanations (e.g., 'to: New recipient(s), or leave empty to keep existing'), adding meaning well beyond the schema's titles.

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 starts with a clear verb+resource ('Update an existing email draft in Gmail') and distinguishes from siblings like 'draft_email' and 'send_existing_draft' by implying it modifies an existing draft.

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 states 'Only provide the fields you want to change — unchanged fields will be preserved', guiding partial updates. Does not explicitly mention when not to use it, but the context with siblings makes it clear.

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