add_section_break

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

Describes the insertion mechanism but lacks disclosure of side effects (e.g., document mutation), permissions needed, or reversibility. No annotations are provided, so the description carries the full burden, which is insufficient.

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?

Extremely concise and well-structured: a one-sentence purpose, a short explanation of the effect, and a clean parameter list. No redundant information.

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?

Covers the core functionality and parameter meanings. However, it does not mention that the tool modifies an open document, potential prerequisites (e.g., document must be open), or error conditions. The presence of an output schema reduces the need for return value info.

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?

Adds clarity to both parameters: para_id is defined as 'paraId of the paragraph...' and break_type lists acceptable values ('nextPage', 'continuous', etc.). The schema only provides titles and a default, so the description significantly enhances understanding.

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?

Clearly states the action ('Add a section break') and the target resource ('at a paragraph'). Distinguishes from sibling tools like 'add_page_break' by specifying it marks the last paragraph of its section.

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 basic context for when to use (placing a section break) but does not mention when not to use or provide explicit alternatives, such as 'set_section_properties' or 'add_page_break'.

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