insert_paragraph

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

No annotations are provided, and the description only states the basic operation. It does not disclose prerequisites (e.g., document must be open), edge cases (e.g., invalid paraId), or default behavior (e.g., formatting of new paragraph). For a mutation tool, more behavioral context is needed.

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 extremely concise: one sentence explaining the purpose, followed by a list of parameters. Every sentence is necessary and adds value. No 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 and the existence of an output schema, the description covers the core functionality. However, it lacks mention of error conditions (e.g., missing paraId) and prerequisites (e.g., open document). For a document tool set, these details would enhance completeness.

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?

The schema has 0% description coverage, so the description carries full burden. It provides clear explanations for all three parameters: after_para_id (target paraId), text (content), and style (optional with example). This adds meaningful detail beyond the property 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), the resource (new paragraph), and the specific insertion position (after a given paraId). It distinguishes itself from sibling tools like 'insert_text' or 'insert_blockquote' by specifying the exact location.

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 implies usage for adding a paragraph after a specific paragraph but does not explicitly state when to use it over alternatives like 'insert_text' or 'insert_blockquote'. No exclusions or prerequisites are mentioned.

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