word_insert_table_paragraphs

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

No annotations are provided, so the description must carry the behavioral burden. The description only says 'Insert' and specifies an anchor point, but does not disclose that changes are tracked by default (per track_changes parameter), how the tool handles invalid paraIds, or any side effects. It lacks transparency about the mutation behavior.

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, front-loaded sentence that communicates the essential action and target without any wasting words. It is concise and to the point.

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 complexity (4 params) and lack of output schema or annotations, the description is too thin. It omits important context such as insertion order, behavior when after_para_id is not found, and the default for track_changes. The schema covers parameters but not runtime behavior, leaving the agent with gaps in understanding.

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 100%, so the baseline is 3. The description adds no new parameter semantics beyond what the schema already provides; the term 'after a given paraId' merely reiterates the after_para_id parameter's schema description.

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 new paragraphs'), the target location ('into a table cell'), and the exact insertion point ('after a given paraId'). It distinguishes this tool from siblings like word_insert_paragraphs by specifying 'table cell', making the purpose unambiguous.

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 the tool is for adding paragraphs to table cells, which gives some context for use. However, it does not explicitly mention when to use this tool instead of alternatives like word_insert_paragraphs or word_edit_table_paragraphs, nor does it state any prerequisites or exclusions.

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