drop_schema

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

With no annotations, the description carries the full burden of behavioral disclosure. It clearly and prominently warns that executing this tool 'will delete all data', which is the most critical behavioral trait. It does not explicitly say the operation is irreversible or that confirm=true is required, but the schema already documents the confirm parameter.

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 only two sentences, front-loads the action, and includes a high-value warning. Every part contributes useful information; there is no filler or redundancy.

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 two-parameter destructive tool with full schema coverage, the description is complete enough for an agent to understand what will happen and to invoke the tool safely. The schema provides the remaining confirmation details, and no output schema is needed.

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 100%, with both confirm and diagram already described in the input schema. The description adds no new parameter-level meaning, which is acceptable given the schema already fully documents each parameter.

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 states a specific action and resource ('Drop all tables defined in the ER diagram') and is clearly distinguishable from siblings like create_schema, list_entities, and validate_diagram. The destructive purpose is unambiguous.

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 destructive warning strongly implies when it should be considered, but the description does not explicitly state when to use it versus alternatives or when not to use it. There is no mention of safer alternatives for partial or non-destructive operations.

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