schema_query

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

The description adds the key behavior of requiring confirmed=true and returning a preview when confirmed is false/absent. This complements the annotations (destructiveHint=true). No contradiction: description aligns with destructive nature.

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?

Three sentences with no redundancy. Front-loaded with the core purpose. Every sentence is essential: what it does, how it differs, and the confirmation requirement.

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 main purpose, differentiation, and the confirmation workflow. Given no output schema, it doesn't need to detail return values. It is adequate for the tool's complexity.

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?

With 100% schema coverage, the description adds value by framing the sql parameter as DDL statements and explaining the confirmed parameter's preview vs execution behavior. This exceeds the schema's basic descriptions.

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 tool executes DDL statements (CREATE, ALTER, DROP, RENAME), distinguishing it from write_query. The verb 'execute' and the list of DDL verbs provide a specific resource and action.

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?

It explicitly separates from write_query, implying a clear context for DDL vs DML. It also instructs to use confirmed=true after a preview. However, it doesn't explicitly exclude usage for other query types, but sibling tool names imply alternatives.

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