delete_rows

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

Annotations already include destructiveHint=true, and the description reinforces the safety requirement of a non-empty WHERE clause to prevent full-table deletion. It adds the behavioral detail that conditions are AND-connected, which goes beyond the annotation metadata.

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, dense sentence that front-loads the primary action and packs essential constraints without redundancy. Every word contributes to understanding the tool's usage.

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 delete tool with no output schema, the description covers the core invocation: table, required where, and optional schema. It omits return-value and edge-case behavior, but this is acceptable given the destructive nature is already captured by annotations and the safety constraint is highlighted.

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?

The input schema covers 'where' and 'schema' but not 'table'; the description clarifies that 'where' is a column-value mapping joined by AND and emphasizes it must be provided. This adds the safety rationale ('prevent full-table deletion') beyond what the schema field descriptions state.

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 '参数化删除' (parameterized delete) and specifies the resource as a table with WHERE conditions. It unambiguously conveys the delete action and differentiates from sibling update/insert tools.

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 explicitly warns that WHERE is required ('必填防全表误删除') to prevent accidental full-table deletion, offering a concrete safety guideline. It also notes the optional schema with default behavior, though it does not explicitly mention alternative tools.

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