clear_table

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

No annotations, but description explicitly states operation is destructive, irreversible, permanently deletes rows, and preserves structure. Lacks details on permissions or rollback but sufficient for core behavior.

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?

Concise two-sentence action caution, followed by argument list. No unnecessary words, well-structured.

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?

Simple tool with no output schema details needed (exists). Covers main behavior and arguments; could mention edge cases (e.g., empty table) but not critical.

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?

With 0% schema description coverage, description adds value by describing each parameter (workspace, item, qualified_name) with examples (e.g., 'dbo.sales'). Could elaborate on where to find values but adequate.

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?

Clearly states verb 'truncate' and resource 'SQL table', explicitly distinguishes from delete_table by noting structure preservation. Differentiates among siblings like delete_table, clone_table.

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?

Provides caution about destructive nature and requires user confirmation, but no explicit guidance on when to use alternatives like delete_table or when not to use this tool.

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