drop_schema

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

With no annotations provided, the description carries the full behavioral burden, but it only restates the action. For a destructive DDL operation it omits whether the removal is irreversible, what happens to contained objects, and any permission or safety requirements. Cascade behavior is only implied via the schema's cascade flag, not explained here.

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?

A single short sentence that is front-loaded with the action. Nothing is wasted, though the extreme brevity is a result of under-specification rather than disciplined editing.

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 schema-drop tool with no annotations, no output schema, and no stated side effects, prerequisites, or rollback story, the definition is not complete enough for an agent to invoke it safely. The schema covers the parameters but the behavioral context is absent.

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%, so all four parameters (cascade, ifExists, schemaName, connectionName) are already documented in the schema. The description adds no meaning beyond the schema, which is the baseline expectation at high coverage.

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 verb+resource combination ("Remove um schema") clearly states what the tool does and on what object. However, it gives no differentiation from siblings like create_schema, list_schemas, or drop_partition, all of which operate on the same schema domain.

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?

There is no guidance on when to use this tool versus alternatives, no mention of prerequisites (e.g., needing elevated privileges), and no warnings about the consequences of dropping a schema. The agent must infer everything from the name.

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