ecp_mssql_truncate_table

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

No annotations are provided, so the description carries the burden of safety disclosure. 'Irreversible' is a strong and explicit warning, and 'Delete all rows from a table' clearly states the destructive scope. It does not cover secondary details like identity resets or foreign-key restrictions, but the core behavioral risk is well disclosed.

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 short sentences with zero filler. The action is front-loaded and the 'Irreversible' warning is given its own sentence for emphasis. Every word earns its place.

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 simple three-parameter destructive tool, the description is minimally adequate: it conveys the action and irreversibility. However, given the absence of annotations and output schema, it leaves usage context, confirmation behavior, and parameter intent to inference from the schema.

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 0%, so the description must compensate, but it does not explain db_name, table_name, or confirm. The parameter names are somewhat self-explanatory, but the critical confirm gate and what db_name refers to are left entirely to the schema.

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 states a specific action ('Delete all rows') on a clear resource ('a table'), and 'all rows' implicitly distinguishes it from row-level delete and drop-table siblings. It does not explicitly name alternatives or state that the table structure is preserved, so it falls just short of full marks.

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?

There is no guidance on when to use this tool versus alternatives like ecp_mssql_drop_table, ecp_mssql_delete_row, or taking a backup first. The description only warns that the operation is irreversible, but offers no 'use this when...' or 'not when...' context.

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