insert_image_after_paragraph

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

No annotations exist, so the description carries full burden. It fails to disclose error handling, side effects (e.g., mutation), or dependencies like file existence, leaving significant gaps in behavioral understanding.

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 concise, with a single purpose line followed by a clean parameter list. It is front-loaded with the main action, but the bilingual mix may slightly reduce clarity for non-Chinese readers.

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 6 parameters and no output schema details, the description omits usage context, error conditions, and behavioral constraints (e.g., valid indices). Sibling tools exist but no comparative guidance is provided.

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?

With 0% schema coverage, the description compensates by explaining each parameter's purpose, units (inches for dimensions), and allowed values for alignment. However, it could detail default behavior when width/height are null.

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 explicitly states the action (insert image) and the resource (after a specified paragraph), clearly distinguishing it from sibling tools like 'add_image' or 'insert_paragraph_after'.

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 in document editing scenarios but provides no explicit when-to-use guidance or differentiation from alternatives such as 'add_image' or 'insert_table_after_paragraph'.

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