Insert page break into Google Doc

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

Annotations only cover the safety profile (readOnly=false, idempotent=false, destructive=false), while the description adds the non-obvious side effect that inserting shifts every later index and mandates a re-read before subsequent edits. That is meaningful behavioral context beyond the structured 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?

Three tight clauses with zero filler: the action and effect come first, then the validity constraint, then the index-shift caveat. Nothing is repeated from the schema or annotations.

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?

With no output schema needed (the effect is described) and annotations covering the mutation profile, the description supplies the remaining essentials: placement constraints, index sourcing, and the shift side effect. An agent has everything required to call it correctly.

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 the baseline is 3, but the description adds a real constraint not in the schema: the index must fall inside an existing body paragraph and not inside a table/header/footer/footnote. It also points to where valid indexes come from, though it doesn't restate index bounds or documentId handling.

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+resource ('Insert a page break ... of a Google Doc') and immediately describes the effect ('content after it starts on a new page'), which distinguishes it from siblings like insert_text or insert_table.

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?

Gives explicit preconditions (index must be inside an existing body paragraph; not inside table, header, footer or footnote) and routes to the right helpers ('use its startIndex from get_document or find_text'). It also prescribes a required follow-up (re-read with get_document before further index-based edits).

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