batch_update_form

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

Discloses atomicity (partial failure rolls back entire batch), requires forms OAuth scope, and implies destructive nature (modification). No annotations are provided, so the description carries the full burden. It could be improved by noting idempotency or rate limits, but it is adequate and accurate.

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?

Two compact paragraphs with no wasted words. The first sentence captures the core purpose. Details are organized logically: atomicity, usage order, alternatives, and auth scope.

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 the complexity of batch update (multiple request types, atomicity) and the presence of an output schema, the description covers all essential behavioral and contextual aspects: what it does, prerequisites, alternatives, scope requirements, and atomicity behavior. No significant gaps.

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. The description adds value by explaining that each request object must have exactly one key (createItem, updateItem, etc.) and provides a link to full schemas. It also clarifies form_id source (edit URL) and user_google_email (authenticated account), going beyond the 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?

The description clearly states it applies a batch of Forms API edit requests atomically, listing specific operations (add/update/delete questions, reorder, update info, toggle quiz mode). It distinguishes itself from sibling tools like set_publish_settings and get_form by positioning itself as the primary way to modify a form after creation.

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 advises to use get_form first to discover existing itemIds/questionIds, and for publish settings to use set_publish_settings. This provides clear when-to-use and when-not-to-use guidance, with specific alternatives named.

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