create_schema

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

With no annotations provided, the description carries the burden of behavioral disclosure. It does disclose that the tool executes DDL statements and creates tables and foreign key constraints. However, it omits the destructive potential of the dropExisting parameter (dropping existing tables), as well as any permissions or transactional side effects, leaving a meaningful gap for a mutation tool.

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 two sentences with no filler, and the core action is front-loaded. Every word earns its place, making it easy for an agent to parse quickly.

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 description covers the core purpose and side effect of creating tables and constraints, but for a mutation tool with no annotations and no output schema, it lacks important contextual details such as the destructive behavior of dropExisting, what a successful call returns, and whether the operation is transactional. It is adequate for basic invocation but not fully complete.

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 the schema already documents both parameters fully. The description adds no parameter-level semantics beyond what the input schema provides, which places it at the baseline of 3.

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 states a specific verb and resource: 'Create PostgreSQL tables from the ER diagram.' It further clarifies the mechanism ('execute DDL statements to create tables and foreign key constraints'), which clearly differentiates it from sibling tools like generate_sql (which generates SQL without executing) and drop_schema (which removes schema).

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 should be used when you want to create tables from an ER diagram, but it does not explicitly state when to use it versus siblings, nor does it mention any exclusions or alternatives. The context is implied rather than stated.

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