update_draft

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

Discloses that Gmail replaces the whole message so all desired fields must be provided, but does not elaborate on side effects, permissions, or behavior of omitted fields.

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?

Single sentence that is front-loaded, efficient, and directly conveys the key action and constraint.

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?

Without output schema, annotations, or parameter descriptions, the tool description lacks details on return values, required fields beyond draft_id, and contexts like account/password usage, making it incomplete for a 12-parameter tool.

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?

With 0% schema description coverage, the tool description only gives a general principle (pass all fields) without explaining any of the 12 parameters, leaving the agent with insufficient guidance.

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 verb 'Replace' and resource 'draft contents', and distinguishes behavior from other draft tools by noting Gmail replaces the whole message.

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?

Description implies when to use (update draft) and gives critical instruction to pass all desired fields, but lacks explicit comparisons to siblings or when not to use.

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