execute_sql

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

With no annotations, the description carries the full behavioral burden. It usefully discloses supported statement categories, the fully qualified table requirement, and the return shape, but omits important behavioral details such as permission requirements, mutation side effects, transaction behavior, and result limits.

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, front-loaded with the core action and supported statement types, then the qualification rule and return shape. No sentence is wasted.

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 one parameter, no annotations, and no output schema, the description is largely complete: it covers purpose, statement types, qualification requirements, and return shape. It stops short of covering safety or error behavior for arbitrary SQL execution, but the core calling information is present.

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 100%, so the parameter is already documented at baseline. The description adds meaningful semantics beyond the schema: tables must be fully qualified as alias.db.table or alias.db.schema.table, and it previews the return 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?

States a specific verb and resource: running SQL statements on OtterStax. Lists supported statement types (SELECT, DDL, DML, COPY, CREATE SOURCE/STREAM), which helps distinguish it from metadata siblings like list_tables and explain_query, though it does not explicitly name alternatives.

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 usage for executing SQL, but does not say when to prefer execute_sql over siblings such as explain_query or describe_table, nor does it provide exclusions or prerequisites beyond the qualification rule.

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