apply_draft

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

No annotations provided, so description carries full burden. States requires auth prompt and that the result is a draft for review. Lacks details on side effects, error states, or idempotency, but covers core behavior.

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?

Every sentence adds value. Concise, front-loaded with key action and constraint, no wasted words. Under 50 words yet covers purpose, condition, and argument details.

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 one parameter, no output schema, and no annotations, the description adequately covers purpose, input, and outcome. Could mention error cases or result type, but baseline completeness is good.

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 has 0% description coverage, but description adds critical guidance: 'draft_id: From propose_draft_reply or propose_draft_mail.' This provides essential source context for the only parameter.

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 'CREATE the previewed draft in the Drafts folder' and explicitly says 'Never sends', distinguishing it from send-related sibling tools. The verb and resource are specific, and the outcome is described.

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?

Provides a prerequisite ('Requires a fresh platform authentication prompt') and specifies the source of draft_id ('From propose_draft_reply or propose_draft_mail'). Implicitly differentiates from send tools by stating 'Never sends', but could explicitly contrast with apply_send.

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