drop_table

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

Annotations already flag destructiveHint=true, so the safety profile is partly covered, but the description adds valuable non-annotation context: irreversibility, the required confirm flag, and a user-confirmation protocol. It stops short of describing side effects on dependent objects (views, FKs).

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?

Two compact sentences, front-loading the destructive nature and the confirm requirement before the user-confirmation instruction. No wasted words; every clause carries operational weight.

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 destructive tool with no output schema, the description supplies the essential safety contract (irreversible, confirm=true, prompt user), which is enough to call it correctly. It omits details on cascading effects or permission requirements, which would strengthen it further.

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 67% and the schema already documents confirm ('Debe ser true') and database (default connection DB). The description restates the confirm requirement rather than adding syntax or format details for the table or database parameters, so it only marginally exceeds the schema baseline.

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?

States a specific verb+resource (delete a table and its data), which cleanly distinguishes it from delete_records (rows), drop_database (whole DB), and create_table among siblings. An agent can identify the operation without opening the schema.

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?

Gives clear preconditions: irreversible, requires confirm=true, and instructs to ask the user for confirmation first. It does not, however, contrast itself with delete_records or drop_database, leaving the agent to infer the level of destructive scope.

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