tables_db_delete_row

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool performs a deletion, implying a destructive operation, but fails to mention critical details like whether deletions are permanent, reversible, require specific permissions, or have side effects on related data. This leaves significant gaps for a mutation tool.

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, direct sentence with zero wasted words, making it highly efficient and front-loaded. Every word contributes to understanding the tool's core function without unnecessary elaboration.

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 destructive operation with no annotations and no output schema, the description is insufficient. It doesn't address behavioral risks, success/failure outcomes, or contextual nuances like transaction staging (hinted by 'transaction_id' parameter), leaving the agent with incomplete guidance for safe and effective use.

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%, providing clear documentation for all four parameters. The description adds minimal value by implying 'row_id' is the unique identifier for deletion, but doesn't elaborate on parameter interactions or usage beyond what the schema already specifies, meeting the baseline for high schema coverage.

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 ('Delete') and target ('a row by its unique ID'), making the purpose immediately understandable. It distinguishes itself from sibling tools like 'tables_db_delete_rows' (bulk deletion) by specifying single-row deletion, though it doesn't explicitly contrast with all alternatives like 'tables_db_delete_table'.

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 provides no guidance on when to use this tool versus alternatives such as 'tables_db_delete_rows' for bulk operations or 'tables_db_delete_table' for table-level deletion. It also lacks information about prerequisites like required permissions or when deletion is appropriate.

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