batch_delete_records

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

With no annotations, the description bears full transparency burden. It only states 'batch delete' without disclosing effects like irreversibility, partial failures, or permission requirements. This is minimal for a destructive operation.

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 is very concise. It is front-loaded with the key action. However, more detail could be added without losing conciseness, such as a brief usage hint.

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?

No output schema, so the description should explain return behavior, success/failure indication, or partial deletion behavior. It is incomplete for a batch operation. Sibling tools with more details (like get_table_records) highlight this gap.

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 is 100%, so baseline is 3. The description adds no extra meaning beyond what the schema provides (tableName and ids). No clarification of ID format or batch constraints.

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 (batch delete) and resource (table records). It distinguishes from sibling delete_record by implying multiple records, though not explicitly. A more explicit contrast with delete_record would raise it to 5.

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?

No guidance on when to use batch_delete_records vs delete_record or other sibling tools. No prerequisites or disclaimers about batch size or error handling. The description lacks any usage context.

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