db_truncate_table

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

With no annotations provided, the description carries the full burden. It discloses the destructive effect ('removes all rows') and a safety trait ('double approval required'), which is useful. However, it does not explicitly state that the operation is permanent/irreversible or that it may require elevated privileges, which are important behavioral traits for a truncate 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?

The description is a single concise sentence with an em-dash clarification. Every word adds value, and the critical 'double approval required' note is included. It is front-loaded with the action and resource, making it easy to skim.

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 tool with two parameters and no output schema, the description covers the core purpose (truncate all rows) and a critical behavioral nuance (double approval required). It does not describe return values, but these are likely unnecessary for a truncate operation. However, it could have briefly mentioned that this is distinct from deleting rows or dropping the table, which is not present.

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 100% of the parameters with descriptions for 'table' and 'cascade'. The description adds no parameter-specific semantics beyond what the schema already provides, so the baseline of 3 is appropriate.

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 verb 'Truncate' and resource 'a table', and explains the scope by noting it 'removes all rows'. This distinguishes it from sibling tools like db_drop_table (which removes the table structure) and db_delete_rows (which removes specific rows).

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. It does not mention that truncate is more efficient than deleting all rows or that it cannot be filtered. There is no explicit when-to-use, when-not-to-use, or alternative tool reference.

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