delete_table

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

The description notes 'permanently delete', indicating irreversibility, which is important. However, no annotations exist, and the description fails to mention potential side effects like cascading deletions or access requirements.

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 extremely concise (6 words) and front-loaded with the action. While efficient, it could be slightly more verbose to include usage context 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?

For a simple delete operation with one parameter, the description is minimally adequate. However, given no output schema and no annotations, it lacks details about recovery, permissions, or related data impact.

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 100% schema coverage and a single parameter, the description adds the 'permanently' qualifier beyond the schema. The schema already clearly describes the parameter's purpose.

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 tool deletes a table permanently, which is a specific action on a specific resource. It distinguishes from sibling tools like 'delete_column' and 'delete_rows' by explicitly mentioning '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?

No guidance on when to use this tool versus alternatives like deleting rows or moving a table to a folder. The description does not specify context or exclude cases.

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