truncate_table

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

No annotations provided, so description carries full burden. It only mentions the confirmed requirement but does not disclose that truncate is irreversible, resets auto-increment, or requires specific permissions. Incomplete.

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?

Extremely concise (one sentence, 6 words). Front-loads the action. Could be slightly longer to include key behavioral detail without losing brevity.

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?

Lacks essential context for a destructive tool: no mention of irreversible data loss, impact on auto-increment, or prerequisites. No output schema. Incomplete for safe 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?

Schema coverage is 75% (3 of 4 params have descriptions). The description adds 'requires confirmed=true', which slightly reinforces the confirmed parameter but does not explain table, database, or connection beyond what schema provides. Low added value.

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 (TRUNCATE) and resource (a table), and adds a requirement (confirmed=true). It distinguishes from siblings like delete_rows (row-level) but doesn't mention that it removes all rows quickly. Clear but minimal.

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 truncate vs alternatives like delete_rows or drop_table. The only hint is the requirement for confirmation. Lacks context for appropriate usage.

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