delete_cell

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

States destructive action (delete) and prerequisite. No annotations exist, so description carries burden. Could mention error handling or irreversibility, but sufficient for a simple deletion.

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?

Two sentences, no fluff. Action stated first, prerequisite second. Efficient and well-structured.

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?

Has output schema so return values not needed. But lacks details on success/error behavior, resource impact, or edge cases (e.g., invalid cellId). Adequate but not comprehensive.

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 0%; description only restates parameter name 'by cellId' without explaining its format, origin, or that it's likely required despite optional schema. Adds minimal value.

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?

Clear verb ('Delete'), resource ('cell from Colab notebook'), and parameter ('by cellId'). Distinguishes from sibling tools like add_cell or move_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?

Explicit prerequisite: 'Requires an active browser connection via open_colab_browser_connection.' Provides clear context for when to use, though no explicit mention of when not to or alternatives.

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