set_widow_control

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

Description only states the action and parameter descriptions. With no annotations, it fails to disclose additional behavioral traits such as side effects, permissions required, or what happens to orphan lines. Minimal beyond the basic operation.

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 with a clear structure: one-line purpose followed by parameter descriptions. No unnecessary words, 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 and existence of output schema, the description covers the action and parameters adequately. However, it lacks explanation of what widow/orphan control means, which could aid an agent unfamiliar with the concept.

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 has 0% description coverage, so description compensates by explaining para_id as 'paraId of the target paragraph' and enabled as 'True to enable widow control, False to remove it'. This adds meaningful context not present in the 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?

Description clearly states 'Enable widow/orphan control for this paragraph', using a specific verb and resource. It distinguishes itself from sibling tools like set_keep_lines_together and set_keep_with_next by focusing on widow/orphan control.

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 (e.g., set_keep_lines_together). Lacks context for when to enable or disable widow control, leaving selection to the agent without hints.

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