⚠️ DESTRUCTIVE: Insert multiple records in batches. Default batch size 1000. All records must have identical columns.

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

The description includes the warning 'DESTRUCTIVE' and specifies the default batch size and column constraint. However, it lacks details on transactionality, error handling, return value, or whether the operation is atomic, which are critical for a potentially destructive tool with no annotations.

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 short (two sentences) and front-loads the critical warning. It is efficient but could be improved by adding more behavioral context without becoming verbose.

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?

Given the tool's complexity (4 params, no output schema, no annotations), the description is insufficient. It fails to explain return values, error scenarios, performance characteristics, or batch behavior, leaving the agent underinformed for correct invocation.

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 description adds meaning for two parameters: data (must have identical columns) and batch_size (default 1000). However, it does not explain table or database_name beyond what the schema provides. With 0% schema coverage, the description partially compensates but leaves gaps.

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?

Tautological: description restates name/title.

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 explicit guidance on when to use this tool versus alternatives (e.g., execute_write_query for single inserts). The description implies use for batch inserts but does not provide conditions, prerequisites, or contraindications.

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