delete_column

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

In the absence of annotations, the description warns that the action is irreversible and deletes all associated data. It does not cover permissions or side effects like impact on references, but the warning provides sufficient transparency for a delete operation.

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, starting with a clear purpose, then a structured Args/Returns section. No unnecessary words, and every sentence adds value.

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 delete tool, the description covers the irreversible nature, parameter identification, and return format. With no output schema, the stated return type ('Dict with status and message') is adequate. No critical gaps remain.

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?

The input schema lacks descriptions (0% coverage), but the description provides a clear list of parameters (doc_id, table_id, column_id) with brief explanations of what each represents. This compensates fully for the schema gap.

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 'Supprime une colonne d'une table' (delete a column from a table). This distinctively identifies the action and resource, differentiating it from sibling tools like create_column or modify_column.

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?

The description includes an 'Attention' warning about irreversibility and data loss, guiding cautious use. Although it does not explicitly compare to alternatives, the context makes the use case unambiguous among siblings.

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