insert_paragraph_after

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

With no annotations, the description carries full burden but only states the action and return type. It does not disclose behaviors like bounds checking, error handling (e.g., invalid index), side effects on other elements, or whether the document must be open. This is insufficient for a mutation tool.

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: two sentences plus an args list. The main action is front-loaded. Every sentence contributes necessary information without redundancy or fluff.

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 (3 params, no annotations, no output schema details), the description covers the basic purpose and parameters. However, it lacks details on error conditions, safety, or behavioral nuances needed for an agent to use it reliably without additional context. It is minimally adequate.

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 coverage is 0% (no property descriptions), so the description adds meaning by explaining index as 'Paragraph index to insert after', text as 'Text content for new paragraph', and style as 'Optional style name'. This clarifies usage beyond the schema titles, though it could include constraints like index range or valid style names.

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 action ('Insert a paragraph'), the resource ('paragraph'), and the location ('after the specified index'), using a specific verb and differentiating it from similar tools like add_paragraph which likely appends to the end.

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 provides no guidance on when to use this tool versus alternatives (e.g., add_paragraph, insert_image), nor does it mention prerequisites or contexts where it should or should not be used. Only the basic operation is described.

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