notebook_add_cell

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

No annotations are provided, so the description carries the full burden for behavioral traits. It discloses the insertion position behavior (after a specified index) and mentions supported cell types (code, markdown), but doesn't disclose message ordering within the cell type enum (the schema lists code, markdown, raw but description only mentions code and markdown). No mention of whether existing cells shift indices, performance implications, or state changes beyond insertion.

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?

Single sentence that is front-loaded with verb and resource. No wasted words. Every element (action, resource type, insertion point) earns its place.

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?

For a tool with 4 required parameters and no output schema, the description is adequate but minimal. It explains the basic operation but not return value (e.g., success message or cell ID), error conditions (e.g., invalid path, unsupported cell type for raw), or edge cases like inserting at the end. With no annotations and no output schema, more behavioral context would be helpful.

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 baseline is 3. The description doesn't add meaning beyond the schema - it mentions 'code or markdown cell' but the schema already enumerates all three types (code, markdown, raw). No additional semantics for path, index, or source parameters.

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 uses specific verb 'Adds' and resource 'code or markdown cell' with clear scope ('after a specified index'). It distinguishes from siblings like notebook_bulk_add_cells (which adds multiple cells) and notebook_create (which creates a notebook, not a cell).

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 use when adding a single cell at a specific position, but doesn't explicitly guide when to use this vs notebook_bulk_add_cells (for multiple cells) or notebook_edit_cell (for modifying existing cells). No when-not-to-use or alternatives are named.

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