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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the description doesn't need to restate safety. It adds value by disclosing atomicity ('single atomic batch update') and warning about 'index calculation errors' with a phased workflow mitigation. This goes beyond the annotations without contradicting them.

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?

The description is longer than average but well-structured with a core statement, a clear alternative reference, and a WORKFLOW section with headings. The example batch is illustrative and earned its place given the tool's complexity. It could be slightly tighter, but overall every section contributes to usability.

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 tool's extensive operation schema and the presence of an output schema (per context signals), the description is reasonably complete. It covers key decision points (when to use this vs. update_doc_headers_footers, how to avoid index pitfalls) without repeating schema details. It doesn't enumerate all operation types, but the schema handles that.

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 100% for the three top-level parameters, so the baseline is 3. The description adds semantic guidance through concrete examples (e.g., using end_of_segment=true to avoid index math) and clarifies when operation types like create_header_footer should be used. This supplements the schema meaningfully.

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 uses a specific verb+resource: 'Executes multiple low-level document operations in a single atomic batch update.' It clearly distinguishes this from sibling tools by explicitly stating 'For normal header/footer text, prefer update_doc_headers_footers' and scoping create_header_footer to advanced section-break layouts.

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?

It provides explicit when-to-use guidance with a named alternative: 'prefer update_doc_headers_footers' for normal headers/footers, and 'Only use create_header_footer here for advanced section-break layouts.' The recommended two-phase workflow (insert content with end_of_segment=true, then create headers/footers) gives clear operational context.

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