ecp_mssql_drop_table

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

With no annotations provided, the description must carry the burden of behavioral disclosure. It does state 'Irreversible,' which is a critical destructive behavior. However, it omits other important aspects: the required 'confirm' parameter that forces an explicit boolean true, the fact that the operation cannot be undone even if the table contains data, and potential error conditions (e.g., non-existent table). The single warning is useful but insufficient for a destructive 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 very short (one sentence) and front-loads the core action and irreversibility, which is efficient. However, it is under-specified: it omits critical parameter semantics and usage context. It is concise but not appropriately sized—it sacrifices necessary information for brevity. A well-structured description would still be concise while covering key parameters and safety requirements.

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 tool's destructive nature, the presence of a confirm parameter, and the complete absence of annotations and output schema, the description is grossly incomplete. It does not explain the confirm requirement, what happens to dependent objects (if any), or what the return value might be. The description is inadequate for an agent to invoke the tool safely and correctly; it only provides the basic intent.

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 description coverage is 0%, and the description does not mention any of the three parameters (db_name, table_name, confirm) at all. The schema only provides names and types, with confirm constrained to true, but there is no explanation of what db_name or table_name should be, nor that confirm is a safety switch. An agent cannot correctly construct the call without external knowledge. The description fails to compensate for the missing schema descriptions.

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: 'Drop (delete) a table entirely. Irreversible.' It specifies the resource (a table) and the operation (drop/delete), and the irreversibility is highlighted. This distinguishes it from sibling tools like truncate (which removes rows but keeps the table) and delete_database. The purpose is unambiguous and appropriately scoped.

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 offers no guidance on when to use this tool versus alternatives such as ecp_mssql_truncate_table (which removes data but preserves schema) or ecp_mssql_delete_database. It does not mention prerequisites (e.g., table must exist), nor does it caution against accidental use beyond stating 'Irreversible.' No alternative tools are referenced, so an agent has to infer the appropriate context from the name alone.

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