drizzle_run_migrations

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Run pending migrations using drizzle-kit' without mentioning that migrations can modify the database schema, may be irreversible, or may require specific permissions or a database connection. Given the potentially destructive nature of migrations, this lack of disclosure is a significant gap.

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 concise sentence that is front-loaded and directly states the operation. Every word earns its place, with 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?

The tool is simple (one optional parameter, no output schema), so a brief description suffices. However, for a migration tool that may alter the database schema, the description lacks important context such as side effects, prerequisites, and the meaning of 'pending'. It is minimally complete but misses critical operational context.

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 already fully documents the single 'config' parameter with a clear description ('Path to drizzle config file (optional)'). The tool description adds no additional parameter semantics, but since schema coverage is 100%, the baseline of 3 applies.

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 'Run pending migrations using drizzle-kit' clearly states a specific verb ('run') and resource ('pending migrations'), and unambiguously distinguishes it from sibling tools like drizzle_generate_migration (which creates migrations) and execute_query (which runs arbitrary SQL).

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 implies the tool is used to apply pending migrations, but it provides no explicit when-to-use guidance, exclusions, or alternative tool comparisons. It does not state when to prefer this over drizzle_generate_migration or execute_query, so the usage context is only implied.

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