import_sql_into_schema

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

No annotations are provided, so the description carries the burden. It discloses that it creates tables, columns, and relationships, but does not mention potential destructive aspects (e.g., if SQL contains DROP statements) or how existing objects are handled. The prerequisite about schema existence is helpful, but more context would be needed for full transparency.

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 compact and front-loaded with the main action, followed by a brief support note and a clear Args block. Every sentence serves a purpose, and the structure makes it easy to scan.

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 tool's complexity (parsing and applying SQL DDL) and the presence of an output schema, the description covers the essential purpose, prerequisites, and parameters. It does not discuss error handling or partial application behavior, but the core information is sufficient for an agent to decide when to use it.

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 the description fully compensates by explaining each parameter. schema_uuid identifies the target schema, sql is described as DDL text with examples, and branch_name is explained with its default. This adds meaningful semantics beyond the bare parameter names.

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 states the action: import SQL DDL into a schema, creating tables, columns, and relationships. It distinctly differs from siblings like export_schema_sql or manual table creation tools by focusing on full PostgreSQL DDL import.

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 gives a key usage prerequisite: the target schema must already exist. It also notes full PostgreSQL DDL support and mentions branch selection, providing clear context. It does not explicitly compare to alternative tools, but the purpose is clear enough.

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