insert_paragraph

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

Annotations already indicate destructiveHint=true, so the mutation nature is clear. The description adds that it supports DOCX and Google Docs, but does not disclose error behavior, what happens with conflicting file_path and google_doc_id, or the lack of output schema. With annotations covering the safety profile, the description provides adequate but not exceptional transparency.

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 a single concise sentence that conveys the core functionality. It is front-loaded and contains no fluff, though it could benefit from a brief note on parameter roles.

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 complexity (7 parameters, 3 required, no output schema), the description is incomplete. It does not explain the return value, error conditions, or provide sufficient context for correct invocation. The description fails to fully equip an agent to use the tool reliably.

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 43%, below 50%, so the description should compensate. However, the description only mentions '_bk_* id' which vaguely relates to positional_anchor_node_id, but does not explain the other required parameters 'new_string' and 'instruction'. No additional semantics are provided for parameters beyond what the schema offers.

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 verb 'Insert' and the resource 'paragraph', specifies positioning relative to an anchor by _bk_* id, and mentions support for DOCX and Google Docs. This is specific and distinguishes it from sibling tools like add_footnote or replace_text.

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 usage guidelines are provided. The description does not explain when to use this tool versus alternatives such as replace_text or add_footnote, nor does it mention prerequisites or contexts where it is inappropriate.

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