execute_sql

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

With no annotations, description carries burden. Details safe mode behavior, sandbox restrictions, and return type. Does not cover auth, rate limits, or side effects beyond write restrictions.

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?

Well-structured: main purpose first, then safety rules, then Args/Returns. Could be slightly more concise but is informative and front-loaded.

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 presence of output schema (not shown), description doesn't need to explain returns. Covers safety and usage adequately for a single-parameter tool with moderate 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?

Schema coverage 0%, so description compensates by explaining the 'sql' parameter as a query string and adding safe mode context. No format constraints needed for a simple string.

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?

Clearly states it executes SQL queries against a Databend database. Distinguishes from siblings like execute_multi_sql and read-only tools like show_databases.

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?

Provides safety rules and sandbox restrictions for write operations, and references get_session_sandbox_prefix(). Lacks explicit guidance on when to use this tool vs. alternative tools like execute_multi_sql.

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