patch_form_draft

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

With no annotations, the description carries the full burden, yet it does disclose one meaningful behavioral trait: unrelated content is preserved, implying a partial/non-destructive merge rather than a full replace. It omits atomicity (do all operations apply or does one failure roll back?), reversibility, auth requirements, and whether the draft must exist first.

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?

A single front-loaded sentence with no filler. It is efficient, though arguably under-sized for an operation that supports ten distinct mutation kinds.

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?

For a high-complexity tool with a large discriminated-union input, no annotations, and no parameter documentation, one sentence is far too thin. An output schema exists so return values needn't be described, but atomicity, auth, operation coverage, and error behavior are all missing.

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 0%, so the description must compensate for both draft_id and the operations array. It explains neither the draft identifier nor the discriminated union of ten operation types, leaving all meaning to be recovered from the raw 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?

States a specific verb and resource: applying targeted operations to a draft. It's clear this is an in-place edit tool, and 'preserving unrelated content' hints at its patch semantics. However, it doesn't differentiate itself from siblings like update_existing_google_form or create_form_draft, nor hint at the operation types available.

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?

No guidance on when to use this versus publishing, creating, updating, previewing, or undoing. Siblings like publish_form_draft and undo_draft_change strongly imply ordering/alternatives the description never addresses. The agent must infer the whole workflow.

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