text_setParagraphRuleBelow

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

With no annotations, the description carries the full behavioral burden but discloses almost nothing. It does not explain whether toggling ruleOn off removes the rule, whether changes are reversible, what permissions are needed, or how ruleWidth/ruleColor interact.

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 front-loaded sentence with no filler. It is efficiently sized for the small amount of content it chooses to convey, though that content is sparse relative to tool complexity.

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 12-parameter mutation tool with no annotations, no output schema, and 92% of parameters undocumented, this description is far from complete. An agent cannot determine required value formats, defaults, or behavioral effects from it.

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 8% (only document_id has a description), and the tool has 12 parameters with 10 required. The description mentions no parameters at all, so it adds zero meaning beyond the sparse 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?

States a specific verb (add/modify) and resource (paragraph rule below). The word 'below' implicitly distinguishes it from sibling text_setParagraphRuleAbove, but the description does not explicitly name or contrast that alternative.

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 like text_setParagraphRuleAbove, and no prerequisites such as whether the document must be open or how to obtain paragraphIndex. The only hint is the verb 'Add or modify'.

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