text_setKeepOptions

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

No annotations are provided, so the description carries the full behavioral burden. It implies a mutation but says nothing about which paragraph is affected, required targeting context, reversibility, or interaction with existing paragraph settings.

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?

A single tight, front-loaded sentence with no filler. It is appropriately terse per se, though its brevity reflects under-specification for an 8-parameter tool rather than genuine completeness.

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?

For a mutation tool with 8 undocumented parameters, no annotations, and no output schema, the description is far too thin. An agent cannot know what the numeric keep options mean or how the target paragraph is identified.

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 only 13% (just document_id), leaving 7 of 8 parameters undocumented in both schema and description. The description mentions no parameter at all, so keepWithNext (0-5), linesTogether (1-10), startParagraph's enum, and keepWithPrevious are entirely unexplained.

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?

States a specific verb (Set) and resource (keep options), with the parenthetical clarifying the term as widow/orphan control. It is distinguishable from text_setColumns, text_setTabs, and other text_set* siblings, but the description never explicitly contrasts itself with them.

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 when-to-use guidance, no prerequisites, and no alternatives named. The agent is told what the tool does but nothing about when to reach for it versus the many other paragraph-formatting tools in the sibling set.

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