Delete Table

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

No annotations provided, so description carries full burden. It discloses permanent deletion, irreversibility, admin key requirement, and confirmation necessity. However, it could mention potential side effects or dependencies, but it covers the key destructive behavior well.

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 concise with bold section headers, front-loaded purpose, and no unnecessary words. Every sentence adds value, making it easy to scan quickly.

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?

Given the lack of output schema, the description adequately explains return type ('Deletion confirmation') and covers all essential aspects: purpose, usage boundaries, safety, and prerequisites. It is complete for a destructive single-purpose tool.

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 100%, so baseline is 3. Description adds context by reinforcing the safety requirement for the 'confirm' parameter and clarifying the purpose of 'table'. It does not contradict schema and provides helpful real-world usage context.

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 'Permanently delete a RawTree table and its data', providing a specific verb and resource. It also distinguishes itself from siblings like 'describe-table' and 'list-tables' by clarifying it's not for clearing query results or undoing single inserts.

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?

Explicitly states when not to use ('NOT for: Clearing a query result or undoing a single insert'), and provides required safety steps (ask user to confirm exact table name) and prerequisites (admin key).

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