transpile_sql

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

The description mentions it returns transpiled SQL or a syntax error, indicating a pure transformation. However, it does not disclose potential side effects, error handling details, or whether it modifies anything. With no annotations, this is minimally adequate.

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?

Two short lines with a structured Args/Returns section. No redundant words, front-loads the core purpose.

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 simplicity (3 string params, no output schema), the description covers the purpose, parameters, and return value adequately. No gaps for this complexity level.

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 docstring explains each parameter (sql, read_dialect, write_dialect) with brief descriptions, compensating for the 0% schema description coverage. The meaning is clear but could include dialect format or examples.

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 first line clearly states it transpiles a SQL statement to another dialect, specifying the verb (transpile) and resource (SQL dialect conversion). It is distinct from siblings like lint_sql and get_all_table_references.

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 on when to use this tool vs alternatives (e.g., lint_sql for validation). No mention of prerequisites or conditions that make this tool preferable.

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