set_page_break_before

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

No annotations are provided, so the description carries full burden. It states the basic effect (setting a page break) but does not disclose behavioral details such as whether it overrides existing formatting, impacts subsequent paragraphs, or requires specific document permissions. For a mutation tool, more transparency is needed.

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 extremely concise: two sentences in the main body plus a structured args block. Every word is purposeful, with no fluff or 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?

Given the simplicity of the tool (two parameters, no output schema details needed beyond basic confirmation), the description is minimally complete. However, it could mention that it modifies paragraph formatting and that the paragraph must exist, especially given the large number of sibling tools.

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?

With 0% schema description coverage, the description fully compensates by clearly explaining both parameters: 'para_id' as the target paragraph ID and 'enabled' as a boolean to force or remove the page break. This adds essential meaning beyond the raw 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 'Force a page break before this paragraph' clearly states the action (force a page break) and the resource (paragraph). The tool name 'set_page_break_before' further reinforces this, distinguishing it from siblings like 'add_page_break' which inserts a manual break at the cursor position.

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?

The description implies usage when you want to enable or disable a page break before a paragraph via the 'enabled' parameter, but it lacks explicit guidance on when to use this tool versus alternatives like 'add_page_break' or 'set_keep_with_next'. No when-not or exclusion conditions are mentioned.

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