set_keep_lines_together

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

Without annotations, the description carries the burden. It explains that enabled toggles the feature, implying a formatting change. However, it does not disclose potential side effects, such as whether other formatting may be affected or if the operation is reversible.

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 very concise and front-loaded with the purpose statement. The Args list is structured and clear. Every sentence adds value.

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 (boolean toggle on a paragraph), the description is mostly complete. However, it does not mention what the output schema contains, but for a setter this is acceptable. No information about error conditions or required state.

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 add meaning. It explains that para_id is the target paragraph and enabled is a boolean toggle. This adds value over the schema, but the description of para_id is generic and could be more specific.

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 verb (keep) and resource (lines of a paragraph on the same page). It distinguishes from siblings like set_keep_with_next by focusing on lines within a single paragraph, but does not explicitly differentiate from other paragraph formatting tools.

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 on when to use this tool versus alternatives such as set_keep_with_next, set_widow_control, or set_page_break_before. Does not mention any prerequisites or contextual conditions.

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