Delete Table

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

No annotations provided, so the description alone must convey behavior. It clearly states the action is permanent, requires admin key, and cannot be undone. Could mention preconditions like table existence.

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?

Well-structured with bold headings, front-loads purpose, and is fairly concise. A minor redundancy in the Safety section repeating confirmation.

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?

Covers return value, destructive nature, and safety. Without output schema or annotations, it is self-contained but could mention error conditions or interaction with other tools.

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?

Input schema has 100% coverage for both parameters. The description reinforces the purpose of the 'confirm' parameter and ties it to the user confirmation requirement, adding context beyond the schema.

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 specifies the verb 'permanently delete' and the resource 'RawTree table and its data', and explicitly states what the tool is NOT for, differentiating it from sibling tools like 'run-query' or 'insert-*'.

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 the tool (clearing query results, undoing insert) and provides a mandatory usage step (ask user for confirmation). Does not name alternative tools for those cases.

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