⚠️ SCHEMA CHANGE: Import schema from SQL or JSON. Creates tables, indexes, views, triggers. Fails if objects exist without IF NOT EXISTS.

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

With no annotations, description carries full burden. It prominently warns 'SCHEMA CHANGE', discloses creation of multiple object types, and states failure condition when objects exist without IF NOT EXISTS. This is good but could detail transactionality or permission requirements.

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?

Single sentence with no superfluous text. Front-loaded warning immediately signals importance. Every word earns its place despite lack of parameter detail.

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 no output schema and multiple sibling tools, description covers core function and failure case but omits return value, success indicators, and advanced behavior like rollback or partial failures. Adequate but not thorough.

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 coverage is 0%, so description should compensate. It mentions 'SQL or JSON' as input formats but does not explicitly link to the 'format' parameter, nor describes 'schema' or 'database_name' parameters. Virtually no added value over schema structure.

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?

Tautological: description restates name/title.

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?

Provides context that tool fails if objects exist without IF NOT EXISTS, implying use for initial setup or migrations. However, no explicit guidance on when to use this over sibling tools like execute_schema_query or create_table, nor mentions prerequisites or recommended workflows.

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