drop_table

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

With no annotations, the description carries the safety burden. It conveys that the operation is destructive ('Remove') and requires a safety confirmation, which is useful. However, it does not explicitly state irreversibility, side effects on dependent objects, or whether the command will fail if confirm is false, leaving important behavioral gaps.

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 a single, compact sentence that expresses the essential purpose and safety feature with no filler. Each word contributes value, making it appropriately concise and front-loaded.

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, single-action tool with fully documented parameters, the description is adequate but not complete. It omits guidance on when to use, expected return behavior, and consequences of dropping a table, which would be valuable given the lack of annotations and output schema.

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 has 100% coverage, so the baseline is 3. The description adds no parameter-specific meaning beyond the schema; 'safety confirmation' merely echoes the confirm parameter's description. The schema already sufficiently explains connectionId, tableName, and confirm.

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 action ('Remove a table from the database') and the resource being acted upon. It is specific and distinct from siblings like create_table, alter_table, and get_table_schema, so the agent can easily identify when this tool applies.

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 gives no guidance on when to use this tool versus alternatives, prerequisites, or safety checks beyond the confirm flag. It does not mention, for example, backing up data or checking relationships before dropping the table, so the agent lacks context for appropriate invocation.

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