add_page_break

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

With no annotations, the description carries the full burden. It honestly describes the action (insert a page break) but does not disclose behavioral details like whether it modifies the paragraph, requires permissions, or what the output contains. For a simple mutation, this is adequate but not enriched beyond the bare minimum.

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?

Single sentence of 6 words—extremely concise. No redundant information. Every word earns its place.

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 simplicity (2 params, has output schema), the description is incomplete: it does not explain document_handle, nor does it provide usage context among many siblings. The output schema exists but is not referenced; still, the description lacks sufficient detail for correct invocation.

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. It only implies that 'para_id' identifies the target paragraph, leaving 'document_handle' completely unexplained. No semantics for either parameter are added beyond their names.

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 the action: insert a page break after a paragraph. It uses a specific verb (insert) and resource (page break) with a location constraint (after a paragraph), which distinguishes it from siblings like set_page_break_before or add_section_break.

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 is provided on when to use this tool versus alternatives such as set_page_break_before or insert_paragraph. The description does not mention prerequisites, context, or when not to use it, leaving the agent without decision support.

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