drizzle_introspect_schema

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

With no annotations provided, the description must disclose behavioral traits but does not. It only restates the tool name and mentions drizzle-kit. It does not indicate whether the operation is read-only, whether it modifies schema files, requires credentials, or what the output/return value is. This lacks essential behavioral context.

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 sentence with no redundancy. It front-loads the core action ('Introspect database schema') and efficiently names the tool ('drizzle-kit'). Every phrase earns its place, making it appropriately concise and structured.

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 simple tool (1 optional param, no output schema, no annotations), the description should provide enough context for the agent to know what happens on success and how to use it in a workflow. It does not explain what introspection produces, how it relates to config, or any side effects. The brief description leaves significant gaps for practical use.

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 provides a description for the only parameter 'config' ('Path to drizzle config file (optional)'), giving 100% schema description coverage. Per calibration, the baseline is 3, and the tool description adds no additional parameter semantics beyond what the schema already covers.

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 identifies the tool as introspecting the database schema using drizzle-kit, which is a specific verb+resource combination. It is distinct from sibling tools like generate_migration or run_migrations, making its purpose 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?

No guidance is given on when to use this tool versus alternatives. It does not mention any prerequisites, exclusions, or when introspection is appropriate (e.g., before generating migrations). The description simply states what it does without usage context.

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